On Apr 17, 2009, at 7:36 PM, dykang wrote:
> > Hi, > > I was trying to migrate from 0.4 to 0.5, and I noticed a behavior in > 0.5 that wasn't listed in the migration document that I'd like to > disable. It appears that in 0.5, begin no longer allows for > subtransactions by default, and that there is no global flag to turn > this behavior on. Is there a recommended strategy for this other than > search/replace? > > Also, since subtransactions were explicity disabled by default now, is > there some danger to them that I should be aware of when using them? the flag was added so that people understand that the begin() they are issuing is not a real BEGIN. they are forced to understand what a "subtransaction" is. as is typical in python, the two strategies to migrate are search and replace, or just a simple monkeypatch on the Session class to get you through the day. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@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 -~----------~----~----~----~------~----~------~--~---
