Hi, >+1 from me. I have no notes to back it up and my memory is not >helping me here very much but I believe having some issues (maybe >memory leaks?) when transactions were not rolled back if an exception >ocurred. This was in the transaction handling middleware I posted in >this list a couple of months ago (not on a TG app). > > I looked into this some more, and someone had already had a go, I guess some time previously. I hadn't noticed it before as it's in errorhandling.py. So this isn't a behaviour change after all. I fixed up the previous attempt a little, so you can now use the database in an exception handler, and I've added a unit test. I've closed ticket #1185.
This is different behaviour to SQLObject, but I suggest leaving the SO code as it is, for compatibility. Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
