2017-08-17 22:00:37 +05:30
|
|
|
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
|
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
|
|
|
|
|
|
# rubocop:disable RemoveIndex
|
2019-02-15 15:39:39 +05:30
|
|
|
class AddRelativePositionToIssues < ActiveRecord::Migration[4.2]
|
2017-08-17 22:00:37 +05:30
|
|
|
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 = ''
|
|
|
|
|
|
|
|
|
|
# When using the methods "add_concurrent_index" or "add_column_with_default"
|
|
|
|
|
# you must disable the use of transactions as these methods can not run in an
|
|
|
|
|
# existing transaction. When using "add_concurrent_index" make sure that this
|
|
|
|
|
# method is the _only_ method called in the migration, any other changes
|
|
|
|
|
# should go in a separate migration. This ensures that upon failure _only_ the
|
|
|
|
|
# index creation fails and can be retried or reverted easily.
|
|
|
|
|
#
|
|
|
|
|
# To disable transactions uncomment the following line and remove these
|
|
|
|
|
# comments:
|
|
|
|
|
disable_ddl_transaction!
|
|
|
|
|
|
|
|
|
|
def up
|
|
|
|
|
add_column :issues, :relative_position, :integer
|
|
|
|
|
|
|
|
|
|
add_concurrent_index :issues, :relative_position
|
|
|
|
|
end
|
|
|
|
|
|
|
|
|
|
def down
|
|
|
|
|
remove_column :issues, :relative_position
|
|
|
|
|
|
|
|
|
|
remove_index :issues, :relative_position if index_exists? :issues, :relative_position
|
|
|
|
|
end
|
|
|
|
|
end
|
