aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKasper Timm Hansen <kaspth@gmail.com>2018-07-31 09:57:37 +0200
committerGitHub <noreply@github.com>2018-07-31 09:57:37 +0200
commit0f6a4891fee41a083a80292c7b27d5822b6f6db6 (patch)
treef273c3cde0faf7f8108f0555c0d8494d3575bd8c
parentb377e4d6b1d80608d8c9ed2f1137b6aca53db7a9 (diff)
parentb1b585fe08c65c0f9bf76ee5c48aebc8e5488187 (diff)
downloadrails-0f6a4891fee41a083a80292c7b27d5822b6f6db6.tar.gz
rails-0f6a4891fee41a083a80292c7b27d5822b6f6db6.tar.bz2
rails-0f6a4891fee41a083a80292c7b27d5822b6f6db6.zip
Merge pull request #33484 from aditya-kapoor/fix-find-each-description
[ci skip] Fix the outdated description for `find_each`.
-rw-r--r--guides/source/active_record_querying.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/guides/source/active_record_querying.md b/guides/source/active_record_querying.md
index 6233708ad5..a2890b9b7a 100644
--- a/guides/source/active_record_querying.md
+++ b/guides/source/active_record_querying.md
@@ -368,7 +368,7 @@ end
**`:start`**
-By default, records are fetched in ascending order of the primary key, which must be an integer. The `:start` option allows you to configure the first ID of the sequence whenever the lowest ID is not the one you need. This would be useful, for example, if you wanted to resume an interrupted batch process, provided you saved the last processed ID as a checkpoint.
+By default, records are fetched in ascending order of the primary key. The `:start` option allows you to configure the first ID of the sequence whenever the lowest ID is not the one you need. This would be useful, for example, if you wanted to resume an interrupted batch process, provided you saved the last processed ID as a checkpoint.
For example, to send newsletters only to users with the primary key starting from 2000: