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
The various information_schema tables could be expressed as Django models. They would not trigger migrations with with managed = False and could be importable as e.g. django_mysql.models.information_schema, for information_schema.Schemata etc. The only two hacks I can forsee would be:
The db_table param would really need to contain the database and table i.e. information_schema.tablename
The objects managers on many of them should be automatically filtered to ones' own database only by default.
The text was updated successfully, but these errors were encountered:
The various
information_schema
tables could be expressed as Django models. They would not trigger migrations with withmanaged = False
and could be importable as e.g.django_mysql.models.information_schema
, forinformation_schema.Schemata
etc. The only two hacks I can forsee would be:db_table
param would really need to contain the database and table i.e.information_schema.tablename
objects
managers on many of them should be automatically filtered to ones' own database only by default.The text was updated successfully, but these errors were encountered: