d8be981466
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.
20 lines
556 B
Ruby
20 lines
556 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
# rubocop:disable Migration/UpdateLargeTable
|
|
class RemoveProjectsPushesSinceGc < ActiveRecord::Migration
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = true
|
|
DOWNTIME_REASON = 'This migration removes an existing column'
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
remove_column :projects, :pushes_since_gc
|
|
end
|
|
|
|
def down
|
|
add_column_with_default :projects, :pushes_since_gc, :integer, default: 0
|
|
end
|
|
end
|