4 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
Yorick Peterse	e26d993f99	Handle EE edge cases in issues.closed_at migration ... EE seems to have had an outdated schema at some point, leading to some environments not having the right columns in place. This adjusts the migration for `issues.closed_at` so it takes care of those cases, ensuring data can be migrated properly. Fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/4803	2018-02-05 15:07:18 +01:00
Yorick Peterse	f01e9c1ef6	Finish any remaining jobs for issues.closed_at ... In the event of Sidekiq jobs getting lost there may be some rows left to migrate. This migration ensures any remaining jobs are completed and that all data has been migrated. This fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/41595	2018-02-01 16:24:10 +01:00