gitlab-org--gitlab-foss/db/migrate/20170131221752_add_relative_position_to_issues.rb

39 lines
1.4 KiB
Ruby
Raw Normal View History

2017-02-01 13:41:01 -05:00
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.
# rubocop:disable RemoveIndex
2017-02-01 13:41:01 -05:00
class AddRelativePositionToIssues < ActiveRecord::Migration
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!
2017-02-01 13:41:01 -05:00
def up
add_column :issues, :relative_position, :integer
2017-02-01 13:41:01 -05:00
2017-03-02 09:58:41 -05:00
add_concurrent_index :issues, :relative_position
2017-02-01 13:41:01 -05:00
end
def down
remove_column :issues, :relative_position
remove_index :issues, :relative_position if index_exists? :issues, :relative_position
end
2017-02-01 13:41:01 -05:00
end