Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transition all ORM classes to new backend design #1621

Closed
muhrin opened this issue Jun 4, 2018 · 1 comment
Closed

Transition all ORM classes to new backend design #1621

muhrin opened this issue Jun 4, 2018 · 1 comment
Assignees
Labels
Milestone

Comments

@muhrin
Copy link
Contributor

muhrin commented Jun 4, 2018

Currently we have some of the ORM models in the 'old' system whereby the backend being used is selected at import time.

We have developed a new backend design that doesn't rely on using run-time import selection and instead uses a concrete instance of an abstract backend to do all provenance graph interaction. So far we have ported:

  • User
  • Authinfo
  • Log entry

to this new system. We may want a plan to migrate all the ORM classes to the new way of doing things.

The new system has one major advantage which is that multiple backends can be loaded simultaneously (even across types e.g. Django and SQLA).

@sphuber
Copy link
Contributor

sphuber commented Feb 26, 2019

Done and done

@sphuber sphuber closed this as completed Feb 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants