> You can adjust `expire_on_commit` if you're only doing short-term read-only actions.
Can you expand on this? Or link to docs/blog so I can do some research. Google hasn't helped me so far. Why would I want to expire after every commit? --- I agree with your assessment. I think its because every time I call "session". I'm actually saying "session_maker()". So the _flushing attribute will be reset because its a new session instance. On Thursday, March 26, 2020 at 1:02:18 PM UTC-5, Jonathan Vanasco wrote: > > My first guess is two things are going on: > > 1. This is a behavior of `expire_on_commit` on the session. Once you > commit on the Primary database, the object is stale. > https://docs.sqlalchemy.org/en/13/orm/session_api.html > > 2. The session is then trying to read off a Secondary database, but the > row has not yet synced. > > You can adjust `expire_on_commit` if you're only doing short-term > read-only actions. However, I would explore to ensure this is trying to > read off the other database and why. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/sqlalchemy/8185b96d-35cb-4973-a9cf-1e572ebd643b%40googlegroups.com.
