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
28 lines
850 B
Ruby
28 lines
850 B
Ruby
# frozen_string_literal: true
|
|
|
|
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class AlterWebHookLogsIndexes < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
disable_ddl_transaction!
|
|
|
|
# "created_at" comes first so the Sidekiq worker pruning old webhook logs can
|
|
# use a composite index.
|
|
#
|
|
# We leave the old standalone index on "web_hook_id" in place so future code
|
|
# that doesn't care about "created_at" can still use that index.
|
|
COLUMNS_TO_INDEX = %i[created_at web_hook_id]
|
|
|
|
def up
|
|
add_concurrent_index(:web_hook_logs, COLUMNS_TO_INDEX)
|
|
end
|
|
|
|
def down
|
|
remove_concurrent_index(:web_hook_logs, COLUMNS_TO_INDEX)
|
|
end
|
|
end
|