On Friday, November 3, 2017 at 12:03:43 AM UTC-4, jens.t...@gmail.com wrote: > > Thanks Mike! Considering we're planning to migrate to PostgreSQL in a > month or two, how would I go about that (considering there's no strict mode > there). Would the exception be raised on PostgreSQL? >
A manual check is robably best, but the exception is triggered on the flush() when executed in PostgreSQL. Mysql is a bit weird in that it does two things different than most other databases: 1. It allows for sql standards to be disabled 2. the default behavior is to have sql standards disabled. There are a lot of weird behaviors because of this, and I wouldn't be surprised if generating this error is deferred in a transaction. Various behaviors are also different based on the table engine you use too. Since you said this is happening in Pyramid, I suggest running a quick standalone script to ensure the error is happening on the commit and not flush. There is a very small chance you have something setup in Pyramid that is causing the error to bubble up like this. -- 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.
