0fc9f9d3e7
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
18 lines
445 B
Ruby
18 lines
445 B
Ruby
# rubocop:disable Migration/RemoveColumn
|
|
class RemovePriorityFromLabels < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = true
|
|
DOWNTIME_REASON = 'This migration removes an existing column'
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
remove_column :labels, :priority, :integer, index: true
|
|
end
|
|
|
|
def down
|
|
add_column :labels, :priority, :integer
|
|
add_concurrent_index :labels, :priority
|
|
end
|
|
end
|