From 11906ec1031526e7bfa1d6787bd84a03c8c7916b Mon Sep 17 00:00:00 2001 From: Xavier Noria Date: Fri, 13 Mar 2009 01:28:51 +0100 Subject: reword a paragraph in find_each explanation --- railties/guides/source/active_record_querying.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/railties/guides/source/active_record_querying.textile b/railties/guides/source/active_record_querying.textile index 92de246510..c902e457d4 100644 --- a/railties/guides/source/active_record_querying.textile +++ b/railties/guides/source/active_record_querying.textile @@ -811,7 +811,7 @@ Behind the scenes +find_each+ fetches rows in batches of 1000 and yields them on The +:start+ option allows you to configure the first ID of the sequence if the lowest is not the one you need. This may be useful for example to be able to resume an interrupted batch process if it saves the last processed ID as a checkpoint. -Apart from +:order+ and +:limit+, which are used by the method itself, +find_each+ accepts the same options supported by +find+. ++find_each+ accepts the same options as +find+ except for +:order+ and +:limit+. Those two are needed internally and if the options argument include any of them an exception is raised. In addition, you can work by chunks instead of row by row using +find_in_batches+. This method is analogous to +find_each+, but it yields arrays of models instead: -- cgit v1.2.3