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