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
b95da565cd
Enable rubocop for db/**/* and ee/db/**/*
2018-07-25 17:47:12 +08:00
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
70c9ceb7b1
Fix datetime format when migrating new notification settings on MySQL
2016-04-14 18:46:18 -03:00
d11288be95
Use query instead of model on migrations
2016-04-08 16:49:01 -03:00
1a293a4384
Update migration comment
...
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2016-03-30 10:44:20 +02:00
855b2820c1
Improve db migrations for notification settings
...
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2016-03-30 10:44:20 +02:00
73c5a34105
Migrate notification setting from members table
...
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
2016-03-30 10:44:20 +02:00
Jan Provaznik