You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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:
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).
The text was updated successfully, but these errors were encountered: