--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TurboGears Trunk" 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/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---
--- Begin Message ---
On Jul 1, 5:02 pm, Paul Johnston <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have noticed a bug with a TurboGears/SA app, it seemed to be picking
> up old data values on occasions. I believe this is due to the SA
> identity map, and in short I think the answer is to call session.clear()
> before each request.
>
> I've raised a ticket on the TG tracker for
> thishttp://trac.turbogears.org/ticket/1419
>
> Mike - does this seem reasonable? Does the Pylons transaction decorator
> do a session.clear?
a clear() before each request is fine. a totally new session for each
request, plus an explicit cleanup step, even better...allows the GC to
handle the old session, makes it easier to implement more customizable
session scopes (like a session bound to a single connection).
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
--- End Message ---
