diff options
| author | Gosia Ksionek <mksionek@gitlab.com> | 2019-04-12 16:41:59 +0000 |
|---|---|---|
| committer | Marcia Ramos <marcia@gitlab.com> | 2019-04-12 16:41:59 +0000 |
| commit | fb940147736ba6d3a68b6fc769c34cdf6bf6bdef (patch) | |
| tree | 401c4e0e5baf290648e7e401097fac0cb41bd8ad | |
| parent | 3b97ea0a0cca1ed411bf122f2396fae39bf79fc0 (diff) | |
| download | gitlab-ce-fb940147736ba6d3a68b6fc769c34cdf6bf6bdef.tar.gz | |
Add information about moving migrations
Add to docs paragraph about a way of moving EE migrations to CE
if needed
| -rw-r--r-- | doc/development/migration_style_guide.md | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/doc/development/migration_style_guide.md b/doc/development/migration_style_guide.md index bb40c0d32b4..0c326eeb851 100644 --- a/doc/development/migration_style_guide.md +++ b/doc/development/migration_style_guide.md @@ -423,3 +423,9 @@ _namespaces_ that have a `project_id`. The `path` column for these rows will be renamed to their previous value followed by an integer. For example: `users` would turn into `users0` + +### Moving migrations from EE to CE + +When migrations need to be moved from GitLab Enterprise Edition to GitLab Community Edition, +a migration file should be moved from `ee/db/{post_,}migrate` directory in the `gitlab-ee` project to `db/{post_,}migrate` directory in the `gitlab-ce` project. This way +the schema number remains intact, there is no need to modify old migrations, and proper columns, tables or data are added in the Community Edition. |