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
15 lines
467 B
Ruby
15 lines
467 B
Ruby
class AddProjectIdToSubscriptions < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def up
|
|
add_column :subscriptions, :project_id, :integer
|
|
add_foreign_key :subscriptions, :projects, column: :project_id, on_delete: :cascade # rubocop: disable Migration/AddConcurrentForeignKey
|
|
end
|
|
|
|
def down
|
|
remove_foreign_key :subscriptions, column: :project_id
|
|
remove_column :subscriptions, :project_id
|
|
end
|
|
end
|