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
Is it possible to control schemas in more than one database with a smart routing?
Current challenges:
Active schema can no longer be tracked in the connection object.
Management commands now require a database parameter that may conflict in some cases with the existing commands.
Duplication of content types across databases, requires to review the caching behavior (although it seems multi-database friendly)
Requires API decision on how to map dynamic tenants with their database (could be a database field or a model method)
Requires API decision on how to specify the databases that can be used for dynamic tenants (public and CLONE_REFERENCE must always be on every database)
The text was updated successfully, but these errors were encountered:
Is it possible to control schemas in more than one database with a smart routing?
Current challenges:
Active schema can no longer be tracked in the connection object.CLONE_REFERENCE
must always be on every database)The text was updated successfully, but these errors were encountered: