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
Some advanced plugins may want to use the PostgreSQL/Redis databases to keep their own complex states.
Let's add a new base plugin context to provide database management lifecycle events.
We assume that each plugin has its own alembic migrations and self-manage their table schema. The plugin context just performs basic sanity checks such as duplication of table names. More detailed SQL guidelines will be required to prevent database integrity errors when deleting plugin-defined tables without affecting the tables defined by the core.
Technical considerations:
Could we provide a generic common CRUD interface of the database tables defined by plugins for the control panel or some kinds of admin interfaces? (like django.contrib.admin)
The text was updated successfully, but these errors were encountered:
Some advanced plugins may want to use the PostgreSQL/Redis databases to keep their own complex states.
Let's add a new base plugin context to provide database management lifecycle events.
We assume that each plugin has its own alembic migrations and self-manage their table schema. The plugin context just performs basic sanity checks such as duplication of table names. More detailed SQL guidelines will be required to prevent database integrity errors when deleting plugin-defined tables without affecting the tables defined by the core.
Technical considerations:
django.contrib.admin
)The text was updated successfully, but these errors were encountered: