3 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
Rémy Coutable	929c20c2bc	Make the time estimate migrations reversible ... Signed-off-by: Rémy Coutable <remy@rymai.me>	2017-01-24 17:15:37 +01:00
Rémy Coutable	2bf5fe5ede	Rename duplicate migrations and skip them if table/columns are already present ... The time tracking feature was backported from EE to CE, thus the CE migrations should be uniquely named and should skip the actual migration content if the table/columns already exist (that means that the EE migrations were already performed). Signed-off-by: Rémy Coutable <remy@rymai.me>	2017-01-19 21:02:45 +00:00