>
> Perfect, that's what I thought.
Thanks a lot Mike!
--
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.
Sorry:
nullable = False
--
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://
oops Sorry!
Yes, I get the same error when I run the offline generated .sql through
psql.
At this point, I am running SA 1.2.11 and fudging the upgrade function I
can bypass the error above.
Basically, there were few op.drop_table() I had to move to the bottom
(after ### end Alembic commands
Hi Mike,
I bumped up to SA to v0.9.10 and alembic completed successfully adding a
revision. IOW, I didn't have to "fudge" with neither the deadcbed_.py nor
with the .sql (offline).
However, when running either migration (online/offline), I received the
same error as before.
sqlalchemy.exc.Int
Thank you very much Mike!
The older baseline is on v0.9.7 but I am not sure if I can bump it up
'blindly' ... I think all constructs are "vanilla" so maybe it's safe.
In my v0.9.7 based model, I used history_meta recipe (slightly modified
though).
At any rate, after fudging around with some op
hey differ between online (first stack)
and offline (second). Hence, this post.*
*Does that make sense?*
*Question: are online migrations run within a single transaction or not?*
*Thanks!!!*
$ alembic upgrade head
/Users/hp3/.pyenv/versions/2.7.14/envs/server_py2/lib/python2.7/site-
packages
