On May 7, 2010, at 12:56 PM, Ergo wrote: > On 7 Maj, 18:52, Michael Bayer <mike...@zzzcomputing.com> wrote: > >> expire_all() your session. that is why you are seeing your stale cache data >> with a query that does not specify cache. > > Was that added recently ? this happens on subsequent requests in > pylons application that in the end calls meta.Session.remove().
its been there for quite a long time. if you OTOH have called remove(), the next request uses a brand new session. if the request never specifies cache, then you're getting data from the DB transaction and assuming you're working in a transaction isolated context you'll always see just what the transaction sees. > > -- > 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. > -- 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.
