gitlab-org--gitlab-foss/db/migrate/20161031171301_add_project_id_to_subscriptions.rb

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
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 02:27:31 -05:00			`class AddProjectIdToSubscriptions < ActiveRecord::Migration[4.2]`
Add project_id to subscriptions 2016-10-31 13:40:27 -04:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

			`def up`
			`add_column :subscriptions, :project_id, :integer`
Enforce use of add_concurrent_foreign_key This adds a Rubocop rule to enforce the use of add_concurrent_foreign_key instead of the regular add_foreign_key method. This cop has been disabled for existing migrations so we don't need to change those. 2017-02-09 10:52:43 -05:00			`add_foreign_key :subscriptions, :projects, column: :project_id, on_delete: :cascade # rubocop: disable Migration/AddConcurrentForeignKey`
Add project_id to subscriptions 2016-10-31 13:40:27 -04:00			`end`

			`def down`
Add a test which would rollback db and migrate again Closes #29106 2017-03-13 08:36:17 -04:00			`remove_foreign_key :subscriptions, column: :project_id`
Add project_id to subscriptions 2016-10-31 13:40:27 -04:00			`remove_column :subscriptions, :project_id`
			`end`
			`end`