Thanks for pointing me there, Michael. Wasn't aware of that InnoDB feature. Make all sense, now.
On Aug 13, 12:37 am, Michael Bayer <mike...@zzzcomputing.com> wrote: > On Aug 12, 2010, at 7:36 AM, Erich Eder wrote: > > > I've found a strange behaviour when using multiple sessions: A > > committed change to an object in one session does not get reflected in > > the other session, even after a session.expire_all() (or expire() or > > refresh() on the object. In fact, even an explicit query does not > > retrieve the changed data. I'm using MySQL. Further investigation > > showed that it happens only with InnoDB. Using MyISAM produces the > > expected results. Looks like a caching issue with InnoDB. > > its not "caching", its transaction isolation, which is why expire_all() is > not the issue here (and why expire_all() is not really needed by itself with > autocommit=False - rollback() and commit() handle it). at the end, session1 > is still open in its second transaction which has loaded a1.data as 123. > > http://dev.mysql.com/doc/refman/5.0/en/innodb-consistent-read.html > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
