On Monday, March 6, 2017 at 10:21:37 AM UTC-5, Mike Bayer wrote: > > a ROLLBACK is occurring which suggests a different error has occurred > and is being swallowed - the transaction can then not continue. Does > your production environment have logs which would illustrate other > exceptions and reasons for rollbacks prior to this one? It is possible > that something like autoflush on query is causing a flush to fail, > something lime that. >
Can you also share your connection strings for each environment? You should also enable logging on sqlalchemy and the backend server. In my experience with situations like this, a certain approach/command/etc works on one database but not another -- and that triggers the error. When you look at logs and the connection string , it becomes easy to pinpoint. -- 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.