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
James Lopez
c663ca434f
remove unnecessary lower function on SQL
2016-02-04 18:38:11 +01:00
James Lopez
5dc77d7577
refactored migration based on feedback
2016-02-04 15:35:03 +01:00
James Lopez
7b868c61ab
refactored migration and spec based on feedback
2016-02-04 13:20:55 +01:00
James Lopez
ecb174bfea
fixed move project method in migration
2016-02-02 17:28:14 +01:00
James Lopez
94b27f9d79
added TODO to not working method
2016-02-01 15:49:52 +01:00
James Lopez
927ab48101
WIP - refactored migration
2016-02-01 15:47:11 +01:00
James Lopez
7dffec2c43
WIP - add migration
2016-01-29 18:52:49 +01:00