diff options
| author | Małgorzata Ksionek <meksionek@gmail.com> | 2019-04-08 23:32:30 +0200 |
|---|---|---|
| committer | Małgorzata Ksionek <meksionek@gmail.com> | 2019-04-08 23:32:56 +0200 |
| commit | 6ef8cc648698715fa2fab1cb747224e0c9005d80 (patch) | |
| tree | 682177dc92a22ab6996adfa84119384a0e647f72 | |
| parent | 225edb0d2d7737cf52ef5cd358082d08e20feaa4 (diff) | |
| download | gitlab-ce-6ef8cc648698715fa2fab1cb747224e0c9005d80.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..3db2e6da23d 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 + +In the situation when some migrations need to be moved from Enterprise Edition to Community Edition, +a migration file should be moved from `ee/db/migrations` directory to `db/migrations` directory. This way +schema number remains intact, there is no need of modyfing old migrations, but proper columns, tables or data are added in the Community Edition. |