Having both ActiveRecord::Base#each and #find_each possibly unnecessary

ActiveRecord::Base#find_each does iterate over every single record in the model, with the same calling conventions as #each. The difference being that, behind the scenes, multiple records are fetched from the database at a time. I would argue that POLS points toward #each being doing this automatically, since it's very surprising when calling #each nukes database performance and takes forever.

As it stands, #each is practically useless and should never be called due to the load it places in the database. Just making it batch behind the scenes would make the method actually useful. Plus, this could be combined with standard Enumerator practice to composite enumeration methods.

For what it's worth, you may be confusing #find_each and #find_in_batches. The former obeys #each's calling convention (no required params, yields each object in succession), and the latter yields an Array of each batched set of objects.

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.