Hm. I enabled strict mode, and sure enough the warning turns into an exception.
Alas, it seems that the flush() in the above example does not cause the exception, it happens later when the query executes. I was looking for a way to preempt that exception: the code runs within a view function of a Pyramid view handler which commits the transaction outside of the view function. Looks like a manual check is needed :-) On Friday, November 3, 2017 at 12:04:54 PM UTC+10, Mike Bayer wrote: > > the most appropriate way is to set strict SQL mode on your MySQL database: > > https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sql-mode-strict > > -- 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.
