Yup, I've got meta.Session.remove() in the finally clause of the BaseController.
I going to try removing beaker from the middleware next, in case beaker is the one doing the caching. And then maybe try playing with Dozer again. If I figure out what's going on, I'll post my findings. Thanks for your time, Alexandre. Have a good week, --diana On Mon, Jan 11, 2010 at 8:40 AM, Alexandre Conrad <[email protected]> wrote: > 2010/1/11 Waldecir Santos <[email protected]>: >> Maybe sqlalchemy cache ? btw this is not a wrong behavior, check the time of >> the second query, if it is faster than the first query, then it is the >> cache. > > I don't think SQLAlchemy has caching. Maybe you should make sure your > session has been closed after the request returned. Otherwise all your > objects might keep living in the UOW of SA. > > in lib/base.py make sure you have something like: > > def __call__(self, environ, start_response): > try: > return WSGIController.__call__(self, environ, start_response) > finally: > meta.Session.remove() > > (or "meta.Session.close()")
-- You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en.
