delta/gitlab/gitlab-ce.git - gitlab.com: gitlab-org/gitlab-ce.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-04-04	1	-3/+3
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2020-03-18	1	-3/+3
\|
*	Add latest changes from gitlab-org/gitlab@master	GitLab Bot	2019-10-29	1	-0/+2
\|
*	Disallow methods that copy data on large tables	Sean McGivern	2018-06-19	1	-0/+20
\| \| \| \| \| \|	{change_column_type,rename_column}_concurrently both copy data from one column to another during a migration, which should not be done on GitLab.com. Instead, we should use background migrations.
*	Use gitlab-styles	Rémy Coutable	2017-12-22	1	-5/+5
\| \| \| \|	Signed-off-by: Rémy Coutable <remy@rymai.me>
*	Prevent update_column_in_batches on large tables	Sean McGivern	2017-11-17	1	-0/+69
	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.