Both are using postgres. But I did try updating the bind to both the engine (db.engine) and the session (db.session) and it didn't have any affect.
On Monday, October 9, 2017 at 2:09:02 PM UTC-7, Jonathan Vanasco wrote: > > OTOMH (I didn't go through your code), are the two databases the same? > > If not, this is possibly related to database specific compiling (or the > lack of) and a common error. Note the `bind` references in the docs: > http://docs.sqlalchemy.org/en/latest/core/tutorial.html#executing > Depending on how you invoke a select, the statement will either be > compiled as a generic string or sqlalchemy knows that it should be > customized for the specific database. Depending on the database, the > generic version will or will not work. This might not be happening -- I > didn't go through your code -- but many situations of "It works when I ___ > but not when I ____" are related to 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.
