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
706 B
Ruby
25 lines
706 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 RemoveIndex
|
|
class AddIndexToUserGhost < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
# When a migration requires downtime you **must** uncomment the following
|
|
# constant and define a short and easy to understand explanation as to why the
|
|
# migration requires downtime.
|
|
# DOWNTIME_REASON = ''
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
add_concurrent_index :users, :ghost
|
|
end
|
|
|
|
def down
|
|
remove_index :users, :ghost
|
|
end
|
|
end
|