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
Sean McGivern	d8be981466	Prevent update_column_in_batches on large tables ... add_column_with_default is implemented in terms of update_column_in_batches, but update_column_in_batches can be used independently. Neither of these should be used on the specified large tables, because they will cause issues on large instances like GitLab.com. This also ignores the cop for all existing migrations, renaming AddColumnWithDefaultToLargeTable where appropriate.	2017-11-17 16:56:50 +00:00
Rémy Coutable	b8b9ed55df	Disable Migration/UpdateColumnInBatches for old migrations ... Signed-off-by: Rémy Coutable <remy@rymai.me>	2017-05-29 11:28:23 +02:00
Valery Sizov	793b9a5ced	Improve migration for Multipple issue assignee feature	2017-05-16 23:51:50 +03:00
Valery Sizov	387c4b2c21	Backport of multiple_assignees_feature [ci skip]	2017-05-04 17:11:53 +03:00