0fc9f9d3e7
Add version 4.2 to all existing migrations
...
DB schema generated by a migration may look different in
rails 4 and 5 (because rails 5 may use different default values).
For this reason it's important to explicitly set for which rails
version a migration was written for.
See https://stackoverflow.com/questions/35929869/activerecordmigration-deprecation-warning-asks-for-rails-version-but-im-no/35930912#35930912
2018-11-22 13:18:28 +01:00
af8cc2e064
Use `remove_foreign_key :timelogs, name: '...'`
...
Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9908#note_25324225
2017-03-14 20:13:36 +08:00
67729cecc1
Add a test which would rollback db and migrate again
...
Closes #29106
2017-03-14 02:12:55 +08:00
85a98fd40f
Refactor migration to not require downtime
2017-02-07 10:42:42 -05:00
bdc9322450
Use normal associations instead of polymorphic.
...
We can't properly use foreign keys on columns that are configured for
polymorphic associations which has disadvantages related to data
integrity and storage. Given we only use time tracking for Issues and
Merge Requests we're moving to the usage of regular associations.
2017-02-07 10:41:44 -05:00
Jan Provaznik