Mike Bayer <mike...@zzzcomputing.com> writes: > That's the normal mechanics of how the ORM does inserts. For columns that > have no default value, it supplies None explicitly. There's some obscure > history behind that and I'm not sure there's much of a rationale beyond > that it makes it easier to cache the INSERT statement and make use of > executemany(). Its been that way for over 10 years so I'm not quick to > just change those things unless it is really causing a problem.
Ok, not a problem at all, just I didn't notice that behavior before (I tend to work at the core layer...), and wasn't sure about it being an error on my configuration. > If these columns have a server side behavior for INSERT then you'd also add > server_default=FetchedValue() and then you wouldn't see the None on INSERT. Thank you, ciao, lele. -- nickname: Lele Gaifax | Quando vivrò di quello che ho pensato ieri real: Emanuele Gaifas | comincerò ad aver paura di chi mi copia. l...@metapensiero.it | -- Fortunato Depero, 1929. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
