Rails Ruby on Rails

Comments and changes to this ticket

• 

  Rizwan Reza May 21st, 2010 @ 12:42 AM

  • no changes were found...
• 

  Santiago Pastorino February 2nd, 2011 @ 04:38 PM

  • State changed from “new” to “open”
  • Importance changed from “” to “Low”

  This issue has been automatically marked as stale because it has not been commented on for at least three months.

  The resources of the Rails core team are limited, and so we are asking for your help. If you can still reproduce this error on the 3-0-stable branch or on master, please reply with all of the information you have about it and add "[state:open]" to your comment. This will reopen the ticket for review. Likewise, if you feel that this is a very important feature for Rails to include, please reply with your explanation so we can consider it.

  Thank you for all your contributions, and we hope you will understand this step to focus our efforts where they are most helpful.

• 

  Santiago Pastorino February 2nd, 2011 @ 04:38 PM

  • State changed from “open” to “stale”

• You flagged this item as spam.
  

  bingbing March 26th, 2011 @ 02:06 AM

  louis vuitton watches

• You flagged this item as spam.
  

  swalterd April 6th, 2011 @ 05:20 PM

  I would like something like this in Rails. Either as the default for dependent => :destroy or as an another dependent option. Like :destroy_in_batches. For an object that has a lot of associated objects, and when each of those objects has many associated objects, the memory cost of loading all of them into before your run the destroy is high. Right now to solve the problem we do two things. First we do a soft delete of the object and then kick off a delayed job to do the real delete. But then we also have to create before_destroy methods for some associations for speed and memory consumption reasons. These then do the batch destroy.