I'm doing some work where I want to rescue ActiveRecord::RecordNotSaved from a save! call nested deep in the code. The thing is there could theoretically be failures here I want to pass through, and I want to inspect the record in order to decide.
I figure a custom initializer on the exception class and a couple quick patches here and there in the code would make it minimally intrusive. I was thinking of whipping up a patch, but I wanted to ask here if there is some reason we definitely don't want AR records attached to exceptions (memory leak risk or some other consider I'm not aware of). What are everyone's thoughts on the feature? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/rubyonrails-core?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
