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
bc00806a4e
Add database helpers 'add_timestamps_with_timezone' and 'timestamps_with_timezone'
2017-06-13 22:44:13 +11:00
c33b489853
Add `null: true` to timestamps in migrations that does not define it
...
This is to ensure that migrations will still be consitent when we will
upgrade to Rails 5 which default to `null: false` for timestamps
columns.
Fixes #23666 .
Signed-off-by: Rémy Coutable <remy@rymai.me>
2016-11-28 16:45:08 +01:00
892dea6771
Project tools visibility level
2016-09-01 11:47:59 -03:00
Jan Provaznik