2015-09-22 10:41 GMT-07:00 Mike Bayer <mike...@zzzcomputing.com>:

>
> So one more time, with all detail possible; attached is an env.py script
> and a full log of all SQL emitted and commands; we have alembic_version is
> created in "public", the two tables created only in "notifications", no
> redundant FK commands in the next run.  Please start with a brand new,
> definitely completely empty PG database, no dependencies, and run this
> env.py as is without any of your application being imported, then do a
> line-by-line on your logs vs. the logs (use logging config in attached
> alembic.ini) here to see where they diverge.  thanks!
>
>
>
>
>
>
>
> Could you reproduce that?
>
>
Ok, I reproduced it on a new database I changed nothing except the script
location in the ini file, and the second revision was fine, no foreign keys
dropped. I'll now slowly change this "good" env.py and .ini to make it more
like my previous one, and see when the issue starts triggering.

-- 
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.

Reply via email to