On 9/22/15 2:25 PM, Sergi Pons Freixes wrote:
2015-09-22 10:44 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com
<mailto:mike...@zzzcomputing.com>>:
On 9/22/15 1:41 PM, Sergi Pons Freixes wrote:
Additional update: If on the env.py I substitute "__table_args__
= {'schema': 'notifications'}" for "__table_args__ = {'schema':
'notifications'}" and rerun alembic twice again (assuming we
start on a clean database), alembic_version is created on the
'notifications' schema, t1 and t2 on 'notifications' schema, and
the issue is done (i.e., the second run of alembic does nothing).
does your PG database have some kind of replication or triggering
happening that is duplicating tables between the two schemas?
Please run everything clean with full logging turned on as I
illustrated in my previous email, you should only see "CREATE
TABLE alembic_version" without any schema qualifier.
Just to be sure: I should create a new database (test) AND the
'notifications' schema, right? Alembic shouldn't be able to create t1
and t2 if the schema didn't exist previously.
yes, alembic doesnt create the schema for you.
--
You received this message because you are subscribed to the Google
Groups "sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to sqlalchemy-alembic+unsubscr...@googlegroups.com
<mailto:sqlalchemy-alembic+unsubscr...@googlegroups.com>.
For more options, visit https://groups.google.com/d/optout.
--
You received this message because you are subscribed to the Google Groups
"sqlalchemy-alembic" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sqlalchemy-alembic+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
