> Stack trace generation is somewhat expensive. throw doesn't do that, > just unwinds the stack up to the catch.
The exception implementation was much much simpler, so I've attached it to the ticket. http://dev.rubyonrails.org/attachment/ticket/8030/sqlite-safe-rollback.diff Heads up to anyone using transaction.rollback!, once I commit this (in the next 48 hours, barring objections) your code may do funny things if you were expecting statements to execute after rollback! was called. -- 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 -~----------~----~----~----~------~----~------~--~---
