1ab33b15d1
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.
8 lines
231 B
Ruby
8 lines
231 B
Ruby
# rubocop:disable Migration/RemoveColumn
|
|
class RemoveNotificationLevelFromUsers < ActiveRecord::Migration
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
def change
|
|
remove_column :users, :notification_level, :integer
|
|
end
|
|
end
|