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
25 lines
868 B
Ruby
25 lines
868 B
Ruby
class EnsureRemoteMirrorColumns < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
# rubocop:disable Migration/Datetime
|
|
add_column :remote_mirrors, :last_update_started_at, :datetime unless column_exists?(:remote_mirrors, :last_update_started_at)
|
|
add_column :remote_mirrors, :remote_name, :string unless column_exists?(:remote_mirrors, :remote_name)
|
|
|
|
unless column_exists?(:remote_mirrors, :only_protected_branches)
|
|
add_column_with_default(:remote_mirrors,
|
|
:only_protected_branches,
|
|
:boolean,
|
|
default: false,
|
|
allow_null: false)
|
|
end
|
|
end
|
|
|
|
def down
|
|
# db/migrate/20180503131624_create_remote_mirrors.rb will remove the table
|
|
end
|
|
end
|