d3d9077830
This works the same way as change_column_type_using_background_migration, but for renaming a column. It takes a table, not a relation, to match its concurrent counterpart. Also, generalise the cleanup migrations to reduce code duplication.
14 lines
422 B
Ruby
14 lines
422 B
Ruby
# frozen_string_literal: true
|
|
|
|
module Gitlab
|
|
module BackgroundMigration
|
|
# Background migration for cleaning up a concurrent column rename.
|
|
class CleanupConcurrentRename < CleanupConcurrentSchemaChange
|
|
RESCHEDULE_DELAY = 10.minutes
|
|
|
|
def cleanup_concurrent_schema_change(table, old_column, new_column)
|
|
cleanup_concurrent_column_rename(table, old_column, new_column)
|
|
end
|
|
end
|
|
end
|
|
end
|