Commit Graph

2 Commits

Author SHA1 Message Date
Sean McGivern d1c761b3e9 Make epic_issues relative_position migration more 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.
2019-09-04 15:25:50 +01:00
Heinrich Lee Yu b4b1f69a0b Remove default relative_position value
This makes `epic_issues` consistent with other tables
using our `RelativePositioning` class
2019-08-09 10:04:08 +08:00