>From reading the docs, it sounds like calling .close() on a session implicitly does a .rollback():
"When the Session is closed, it remains attached, but clears all of its contents and releases any ongoing transactional resources, including rolling back any remaining transactional state. The Session can then be used again." But, it looks like this may not be the case? I have an application that reads data from a MySQL db using InnoDB tables and the session is set to transactional. I believe this defaults me into MySQL's "repeatable read" consistency level. If I select some data, .clear()/.close() the session, change the data from another connection and then re-read the data using the original session I get the old data. If I do a commit() I can then see the new data. This makes me think that .close() is not doing a rollback so MySQL keeps returning the same data for every select regardless of whether it has changed in the DB. Or am I missing something else? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
