>
> 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
you can change the nullability of a column with op.alter_column().
There's no need to create a separate constraint.
On Thu, Sep 6, 2018 at 8:07 PM, HP3 wrote:
> Sorry:
>
> nullable = False
>
> --
> You received this message because you are subscribed to the Google Groups
> "sqlalchemy-alembic"
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
On Thu, Sep 6, 2018 at 1:14 PM, HP3 wrote:
> Hello,
>
> As I try alembic (for the first time), I ran into the following stack traces
> when attempting to conduct a "nasty" migration.
>
> I call it "nasty" because the original model was based on sqlalchemy v0.9 +
> python 2.7 and the new model is