mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Fix find_each options [ci skip]
This commit is contained in:
parent
d0ec2a9856
commit
bd41f68f40
1 changed files with 2 additions and 2 deletions
|
@ -317,7 +317,7 @@ end
|
|||
|
||||
The `find_each` method accepts most of the options allowed by the regular `find` method, except for `:order` and `:limit`, which are reserved for internal use by `find_each`.
|
||||
|
||||
Two additional options, `:batch_size` and `:begin_at`, are available as well.
|
||||
Three additional options, `:batch_size`, `:begin_at` and `:end_at`, are available as well.
|
||||
|
||||
**`:batch_size`**
|
||||
|
||||
|
@ -348,7 +348,7 @@ Another example would be if you wanted multiple workers handling the same proces
|
|||
Similar to the `:begin_at` option, `:end_at` allows you to configure the last ID of the sequence whenever the highest ID is not the one you need.
|
||||
This would be useful, for example, if you wanted to run a batch process, using a subset of records based on `:begin_at` and `:end_at`
|
||||
|
||||
For example, to send newsletters only to users with the primary key starting from 2000 up to 10000 and to retrieve them in batches of 1000:
|
||||
For example, to send newsletters only to users with the primary key starting from 2000 up to 10000 and to retrieve them in batches of 5000:
|
||||
|
||||
```ruby
|
||||
User.find_each(begin_at: 2000, end_at: 10000, batch_size: 5000) do |user|
|
||||
|
|
Loading…
Reference in a new issue