Here is a simplified version of my scenario: My application has two session objects. One is being used for editing certain data, and the other is reading this data, doing some calculations, and displaying the results. I've set up a callback kind of system so that whenever the first session does a commit, a method is called that does a rollback on the second session, and redoes the calculations and display. I've had bugs crop up where the data I get from querying the second session object doesn't match what I know is in the database, but I haven't been able to reproduce them consistently yet. So my questions are:
1. After a session.rollback(), should the data obtained from that session's queries match what's in the DB now? Or what was in the DB when the session was created? The docs<http://www.sqlalchemy.org/docs/orm/session.html#sqlalchemy.orm.session.Session.rollback> are not clear on this. 2. If a rollback is not enough to guarantee that the data from querying a session is up to date, then what is? Should I just create a new session entirely? cheers, Cam Cameron Jackson Engineering Intern Air Operations Thales Australia Thales Australia Centre, WTC Northbank Wharf, Concourse Level, Siddeley Street, Melbourne, VIC 3005, Australia Tel: +61 3 8630 4591 cameron.jack...@thalesgroup.com.au<mailto:cameron.jack...@thalesgroup.com.au> | www.thalesgroup.com.au<http://www.thalesgroup.com.au> ------------------------------------------------------------------------- DISCLAIMER: This e-mail transmission and any documents, files and previous e-mail messages attached to it are private and confidential. They may contain proprietary or copyright material or information that is subject to legal professional privilege. They are for the use of the intended recipient only. Any unauthorised viewing, use, disclosure, copying, alteration, storage or distribution of, or reliance on, this message is strictly prohibited. No part may be reproduced, adapted or transmitted without the written permission of the owner. If you have received this transmission in error, or are not an authorised recipient, please immediately notify the sender by return email, delete this message and all copies from your e-mail system, and destroy any printed copies. Receipt by anyone other than the intended recipient should not be deemed a waiver of any privilege or protection. Thales Australia does not warrant or represent that this e-mail or any documents, files and previous e-mail messages attached are error or virus free. ------------------------------------------------------------------------- -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@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.
