diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-19 18:44:42 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2021-05-19 18:44:42 +0300 |
| commit | 4555e1b21c365ed8303ffb7a3325d773c9b8bf31 (patch) | |
| tree | 5423a1c7516cffe36384133ade12572cf709398d /doc/development/avoiding_downtime_in_migrations.md | |
| parent | e570267f2f6b326480d284e0164a6464ba4081bc (diff) | |
Add latest changes from gitlab-org/gitlab@13-12-stable-eev13.12.0-rc42
Diffstat (limited to 'doc/development/avoiding_downtime_in_migrations.md')
| -rw-r--r-- | doc/development/avoiding_downtime_in_migrations.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/development/avoiding_downtime_in_migrations.md b/doc/development/avoiding_downtime_in_migrations.md index d8981ce0999..6b6c47cfece 100644 --- a/doc/development/avoiding_downtime_in_migrations.md +++ b/doc/development/avoiding_downtime_in_migrations.md @@ -365,6 +365,12 @@ if the application no longer uses the table. Renaming tables requires downtime as an application may continue using the old table name during/after a database migration. +If the table and the ActiveRecord model is not in use yet, removing the old +table and creating a new one is the preferred way to "rename" the table. + +Renaming a table is possible without downtime by following our multi-release +[rename table process](database/rename_database_tables.md#rename-table-without-downtime). + ## Adding Foreign Keys Adding foreign keys usually works in 3 steps: |