5 commits

Author	SHA1	Message	Date
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
Dmitriy Zaporozhets	a9eba1bde0	No need to block db:rollback for safe migration	2015-02-25 19:51:13 -08:00
Marco Wessel	b19b8c679a	Give last_activity_at a default value so it will always be set	2015-02-23 03:36:21 +01:00