diff options
Diffstat (limited to 'doc/development/background_migrations.md')
| -rw-r--r-- | doc/development/background_migrations.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/development/background_migrations.md b/doc/development/background_migrations.md index df3baa3349e..695c565ca83 100644 --- a/doc/development/background_migrations.md +++ b/doc/development/background_migrations.md @@ -8,7 +8,7 @@ info: "See the Technical Writers assigned to Development Guidelines: https://abo # Background migrations Background migrations should be used to perform data migrations whenever a -migration exceeds [the time limits in our guidelines](database_review.md#timing-guidelines-for-migrations). For example, you can use background +migration exceeds [the time limits in our guidelines](migration_style_guide.md#how-long-a-migration-should-take). For example, you can use background migrations to migrate data that's stored in a single JSON column to a separate table instead. @@ -18,7 +18,7 @@ migrations automatically reschedule themselves for a later point in time. ## When To Use Background Migrations You should use a background migration when you migrate _data_ in tables that have -so many rows that the process would exceed [the time limits in our guidelines](database_review.md#timing-guidelines-for-migrations) if performed using a regular Rails migration. +so many rows that the process would exceed [the time limits in our guidelines](migration_style_guide.md#how-long-a-migration-should-take) if performed using a regular Rails migration. - Background migrations should be used when migrating data in [high-traffic tables](migration_style_guide.md#high-traffic-tables). - Background migrations may also be used when executing numerous single-row queries |