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
20 lines
623 B
Ruby
20 lines
623 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class AddSquashToMergeRequests < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
disable_ddl_transaction!
|
|
|
|
DOWNTIME = false
|
|
|
|
def up
|
|
unless column_exists?(:merge_requests, :squash)
|
|
# rubocop:disable Migration/UpdateLargeTable
|
|
add_column_with_default :merge_requests, :squash, :boolean, default: false, allow_null: false
|
|
end
|
|
end
|
|
|
|
def down
|
|
remove_column :merge_requests, :squash if column_exists?(:merge_requests, :squash)
|
|
end
|
|
end
|