I ran into the issue that the sessioning implementation in sqlalchemy doesn't let you perist objects throughout a cherrypy request cycle - a clear in run_with_transaction destroys anything created earlier
the solution? pushing the clear into a cherrypy filter that starts on request startup, then changing the clear to a begin() in run_with transaction this will work with sqlalchemy < .20 , not sure about the .20 solution http://trac.turbogears.org/turbogears/ticket/870 unfortunately, doing this would require integrating the filter. i'm not sure the best way to do that - maybe where sqlalchemy is first imported, or a connection is made? this also made me thing that it might be beneficial if a db begin() end() happened at the request start and finalize stages. i belive sqlalchemy and sqlobject both support nested transactions like that. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
