Schema-Level Multi Tenancy for PostgreSQL Databases - Edge Case #1496
Unanswered
biyani701
asked this question in
Usage Questions
Replies: 1 comment
-
Hi, I haven't tried this particular suggestion, but if I understand it correctly the tables in the public schema should not be detected when setting a schema that's no public, so in your first run with Could you provide your env.py? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my models few tables need to be created in public schema and remaining tables in the specific schema
Referencing https://alembic.sqlalchemy.org/en/latest/cookbook.html section "Rudimental Schema-Level Multi Tenancy for PostgreSQL Databases", in the first pass if i pass the schema first_schema, the tables are created
Now if i run the migration with second_schema, because the tables in public schema exists, the migration run fails,.
Is it possible to handle this by adding some hooks?
Databases / Backends / Drivers targeted
postgresql+psycopg2Example Use
Additional context
Have a nice day!
Beta Was this translation helpful? Give feedback.
All reactions