Could you run your code within a transaction and call the existing `destroy` method, and then rollback the transaction in the case that you don't want the deletion to persist?
Can you share some real world examples showing why you'd need to be able to soft delete the associated records? There might be other, better workarounds. My guess is that this would be a complicated feature to add, but I'm not too familiar with the parts of ActiveRecord that this would touch. -- 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 https://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
