We’ve been having an interesting problem in a Galera configuration: 1. We get a session.
2. We add a row with session.add() 3. We commit with session.commit() 4. Using the SAME session, we then try and get the same row. 5. We get row not found. We believe that what’s happening is the get is using a different pool connection than the add, so Galera perceives it as a different session, and directs it to a different instance, which may not have the commit() yet. We would think that we could avoid this by using the same session, but maybe not. Is there a way to force the add() and get to use the same connection across commit()? Thanks! -- 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.
