gitlab-org--gitlab-foss/db/migrate/20160610194713_remove_depre...

# rubocop:disable Migration/RemoveColumn
class RemoveDeprecatedIssuesTrackerColumnsFromProjects < ActiveRecord::Migration[4.2]
  def change
    remove_column :projects, :issues_tracker, :string, default: 'gitlab', null: false
    remove_column :projects, :issues_tracker_id, :string
  end
end
Add cop for use of remove_column remove_column should only be used in the up (or change) step of a migration if it's a post-deployment migration. Otherwise there will be downtime due to the ActiveRecord column cache, which we can avoid by using the IgnorableColumn concern in combination with a post-deployment migration. 2017-12-11 16:34:51 +00:00			`# rubocop:disable Migration/RemoveColumn`
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 RemoveDeprecatedIssuesTrackerColumnsFromProjects < ActiveRecord::Migration[4.2]`
Remove deprecated issues_tracker and issues_tracker_id from project 2016-06-10 19:53:20 +00:00			`def change`
			`remove_column :projects, :issues_tracker, :string, default: 'gitlab', null: false`
			`remove_column :projects, :issues_tracker_id, :string`
			`end`
			`end`