On 9/26/07, -a <[EMAIL PROTECTED]> wrote: > summary: > > http://drawohara.tumblr.com/post/12411960 > > i am the only one thinking along these terms?
Please see http://dev.rubyonrails.org/ticket/5457 and search Trac for 'nested transaction' or 'savepoint' for others. > is there some rationale i'm missing behind the current behaviour? Yes, though you've blanketed the possibility with "the standard activerecord transactions are not sane." The current behavior -- flattening successive 'I require a transaction' declarations in the app into a single database transaction -- is precisely what most developers writing most web apps need. Explicitly nesting transactions or emulating them with a proliferation of savepoints are sexy features, but do they make sense at the application level? Does their exposure increase programmer happiness or their blood pressure? I hope you contribute your work to #5457. Incremental, fully-tested changes to the existing API are most welcome. The underlying features your propose are solid and needn't be roaming the countryside tilting at sanitoriums ;) jeremy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-core@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
