gitlab-org--gitlab-foss/db/migrate/20170407140450_add_index_to...

# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.

class AddIndexToNextRunAtAndActive < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  DOWNTIME = false

  disable_ddl_transaction!

  def up
    add_concurrent_index :ci_trigger_schedules, [:active, :next_run_at]
  end

  def down
    remove_concurrent_index :ci_trigger_schedules, [:active, :next_run_at]
  end
end
Update migrations 2017-04-07 14:06:51 +00:00			`# See http://doc.gitlab.com/ce/development/migration_style_guide.html`
			`# for more information on how to write migrations for GitLab.`

Add version 4.2 to all existing migrations 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 2018-11-13 07:27:31 +00:00			`class AddIndexToNextRunAtAndActive < ActiveRecord::Migration[4.2]`
Update migrations 2017-04-07 14:06:51 +00:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

Another round of code review 2017-04-07 15:34:41 +00:00			`disable_ddl_transaction!`

			`def up`
			`add_concurrent_index :ci_trigger_schedules, [:active, :next_run_at]`
			`end`

			`def down`
Yet, another errors 2017-04-07 16:05:39 +00:00			`remove_concurrent_index :ci_trigger_schedules, [:active, :next_run_at]`
Update migrations 2017-04-07 14:06:51 +00:00			`end`
			`end`