diff options
Diffstat (limited to 'doc/development/database/batched_background_migrations.md')
| -rw-r--r-- | doc/development/database/batched_background_migrations.md | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/development/database/batched_background_migrations.md b/doc/development/database/batched_background_migrations.md index edb22fcf436..192cd0d3e49 100644 --- a/doc/development/database/batched_background_migrations.md +++ b/doc/development/database/batched_background_migrations.md @@ -233,7 +233,7 @@ class CopyColumnUsingBackgroundMigrationJob < BatchedMigrationJob end ``` -### Additional filters +## Additional filters By default, when creating background jobs to perform the migration, batched background migrations iterate over the full specified table. This iteration is done using the @@ -276,6 +276,10 @@ In the second (filtered) example, we know exactly 100 will be updated with each end ``` + NOTE: + For EE migrations that define `scope_to`, ensure the module extends `ActiveSupport::Concern`. + Otherwise, records are processed without taking the scope into consideration. + 1. In the post-deployment migration, enqueue the batched background migration: ```ruby |