Jan Provaznik
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
Lin Jen-Shin
b95da565cd
Enable rubocop for db/**/* and ee/db/**/*
2018-07-25 17:47:12 +08:00
Sean McGivern
98bb435f42
Enable RuboCop for migrations
...
Migrations shouldn't fail RuboCop checks - especially lint checks, such
as the nested method check. To avoid changing code in existing
migrations, add the magic comment to the top of each of them to skip
that file.
2016-06-09 16:05:25 +01:00
Kamil Trzcinski
89aed37eef
Make migrations reversible
2015-12-23 19:39:59 +01:00
Kamil Trzcinski
e136a976b6
Fix ci_projects migration by using the value only from latest row [ci skip]
...
This is needed, because for some projects we have duplicate ci_projects.
This was introduced by lack of DB uniqueness on ci_projects.gitlab_id.
2015-12-17 11:09:59 +01:00
Kamil Trzcinski
927c40ca49
Fix Ci::Project migration not migrating columns that cannot be NULL [ci skip]
2015-12-14 12:31:35 +01:00
Kamil Trzcinski
91cdb08d5f
Rename columns and rename migrations
2015-12-11 18:02:09 +01:00
