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
26 lines
731 B
Ruby
26 lines
731 B
Ruby
# rubocop:disable Migration/Timestamps
|
|
class CreateLabelPriorities < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = true
|
|
DOWNTIME_REASON = 'This migration adds foreign keys'
|
|
|
|
disable_ddl_transaction!
|
|
|
|
def up
|
|
create_table :label_priorities do |t|
|
|
t.references :project, foreign_key: { on_delete: :cascade }, null: false
|
|
t.references :label, foreign_key: { on_delete: :cascade }, null: false
|
|
t.integer :priority, null: false
|
|
|
|
t.timestamps null: false
|
|
end
|
|
|
|
add_concurrent_index :label_priorities, [:project_id, :label_id], unique: true
|
|
add_concurrent_index :label_priorities, :priority
|
|
end
|
|
|
|
def down
|
|
drop_table :label_priorities
|
|
end
|
|
end
|