I'm hitting this assert on line 2203 of orm/session.py. I used to hit an error about over 100 subsequent flushes at the same spot. Since updating my SQLAlchemy version yesterday I'm now hitting this instead.
Can anyone with better knowledge of the ORM help me figure out what is happening? * I have expire_on_commit disabled. * When a client connects, the object in question is queried using populate_existing() * The object in question stays in the session the entire duration that the client is connected * One field is periodically updated * Rarely, this error is triggered on the commit after that field is updated * At the time of the error, this object is marked dirty, nothing else is new, dirty, or deleted * Prior to commit, this object is in persistent state Could something being done to a different object (perhaps one connected to this one via a relationship) somehow be causing this? Some other objects change very quickly, and are detached from the session and added back when they need to be persisted. Thanks, Jon -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
