On May 27, 2008, at 7:15 PM, TP wrote:
> > We're using SA 0.4.4. We're creating non-threadlocal sessions that are > bound to an engine at session factory creation time. Any ideas for why > even after closing one session and creating a new session with the > session factory that we're seeing old data? If we do an explicit > commit or rollback, then we start seeing the new data in subsequently > created sessions. I even tried doing refresh() and expire() calls on > the object before closing and re-creating the session, but we still > saw the old data. its not really clear how you could be seeing that. If you are using scoped_session(), the remove() call will actually dispose of the session entirely so you might want to try that; but a close() does remove all connection resources (with the "you're not bound directly to a connection" caveat I mentioned earlier). Send along some code which illustrates exactly how you are configuring your session and what steps you are using to see these results. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
