> If we can disregard breaking any existing code that goes like: > > transaction do |trx| > ... > if there_is_a_problem > trx.rollback! > log 'Oops!' > # other interesting side effects > end > end > > then I'll happily live with (1).
Unless I'm mistaken this mode of using transactions was added during the current trunk phase, and I'm pretty sure that only david uses it. I'll be sure to send a headsup before this list before I commit anything. As for throw/raise. I'm going to wear my newb hat and say I don't really 'get' the difference. But I certainly like the idea of not breaking existing rescue clauses, so throw seems perfect. Does anyone have any objections to using catch(:rollback) throw :rollback? -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
