Thanks for the reply Mike.
This is something I clearly misunderstood, and I realised that late last
night after reading the docs but didn't follow-up here.
The naming is confusing, since `server_default` ends up in the DDL, but
server_onupdate doesn't. Even though the latter is named similar to
onupdate on a Foreignkey, which is server side.
I'll have to go back and add triggers for updated columns that should get
automatically updated when a change occurs. Do you know if there is a
recipe for this already somewhere?
Thanks,
Bert JW Regeer
On Monday, 12 November 2018 08:02:06 UTC-7, Mike Bayer wrote:
>
> server_onupdate is not an actual "server side" construct, it's a
> marker on the client side only to instruct SQLAlchemy that some
> trigger or something set up separately will be changing the value of
> the column when an UPDATE occurs.
> On Mon, Nov 12, 2018 at 1:00 AM Bert JW Regeer > wrote:
> >
> > Hey all,
> >
> > After perusing the documentation, I am just making sure I am not an
> idiot and overlooked something, but is altering server_onupdate possible
> with `alter_coumn`?
> >
> > Thanks,
> > Bert JW Regeer
> >
> > --
> > 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.
>
--
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.
