summaryrefslogtreecommitdiff
path: root/GITLAB_WORKHORSE_VERSION
diff options
context:
space:
mode:
authorSean McGivern <sean@gitlab.com>2019-09-04 13:06:06 +0100
committerSean McGivern <sean@gitlab.com>2019-09-04 15:25:50 +0100
commitd1c761b3e93ec09ba3f77ba7f4b2f229c425bd3c (patch)
tree7e90d9ea0c3a1d84e106717abc45f6f1669f5db5 /GITLAB_WORKHORSE_VERSION
parentf8f8ed471f6ce62b7198d49170845f7f5a09cf64 (diff)
downloadgitlab-ce-d1c761b3e93ec09ba3f77ba7f4b2f229c425bd3c.tar.gz
Make epic_issues relative_position migration more robustmake-epics-position-migration-robust
If someone installed EE, then downgraded to CE before this column was added, upgrading to the latest version of CE will fail: 1. We have a backport migration for the entire EE schema but the table `epic_issues` exists, just not the `relative_position` column. 2. The migration that changes the default (quite reasonably) didn't check if the column exists. If the column doesn't exist, we can just create it with the correct default.
Diffstat (limited to 'GITLAB_WORKHORSE_VERSION')
0 files changed, 0 insertions, 0 deletions