Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

This project is archived and is in readonly mode.

Find in batches when destroying dependent associations

#4660

This is more of an idea I wanted to toss up, if people like it I'll work on a commit. But find_each and find_in_batches are both in ActiveRecord. Wouldn't it make sense for the automatic hooks on destroying associations to use this? Instead of trying to load up all of the objects at once and destroy them.

Reported by Ben Johnson · May 20th, 2010 @ 03:01 PM

State: stale
Milestone: none
Assigned to: nobody
Importance: Low

Activity

  1. Rizwan Reza
    Rizwan Reza
    • No changes were found…

    May 21st, 2010 @ 12:42 AM

  2. Santiago Pastorino
    Santiago Pastorino
    • 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.

    February 2nd, 2011 @ 04:38 PM

  3. Santiago Pastorino
    Santiago Pastorino
    • State changed from open to stale

    February 2nd, 2011 @ 04:38 PM

  4. bingbing
  5. swalterd
    swalterd

    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.

    April 6th, 2011 @ 05:20 PM