gitlab-org--gitlab-foss/db/migrate/20160610301627_remove_notification_level_from_users.rb

# rubocop:disable Migration/RemoveColumn
class RemoveNotificationLevelFromUsers < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  def change
    remove_column :users, :notification_level, :integer
  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 11:34:51 -05: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 02:27:31 -05:00			`class RemoveNotificationLevelFromUsers < ActiveRecord::Migration[4.2]`
Remove notification level fild from users, improve migrations and specs 2016-06-09 15:33:31 -04:00			`include Gitlab::Database::MigrationHelpers`

			`def change`
			`remove_column :users, :notification_level, :integer`
			`end`
			`end`