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
be834c4de9
changed a few things based on feedback
2016-04-11 11:13:51 +02:00
8d7d9c8daa
added missing column for current att_encrypted version
2016-03-21 13:23:35 +01:00
cefefb2ade
WIP - refactored migration and updated project_import_data with encrypted att
2016-03-03 18:10:06 +01:00
Jan Provaznik