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/7cdd3a62-63d3-4b3c-8366-4748fc2256cf%40googlegroups.com.
