gitlab-org--gitlab-foss/db/post_migrate/20170828170516_remove_user_...

# See http://doc.gitlab.com/ce/development/migration_style_guide.html
# for more information on how to write migrations for GitLab.

class RemoveUserExternalMailColumns < ActiveRecord::Migration[4.2]
  include Gitlab::Database::MigrationHelpers

  DOWNTIME = false

  def change
    remove_column :users, :external_email, :boolean
  end
end
Profile updates from providers 2017-08-29 08:57:41 +00:00			`# See http://doc.gitlab.com/ce/development/migration_style_guide.html`
			`# for more information on how to write migrations for GitLab.`

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 RemoveUserExternalMailColumns < ActiveRecord::Migration[4.2]`
Profile updates from providers 2017-08-29 08:57:41 +00:00			`include Gitlab::Database::MigrationHelpers`

			`DOWNTIME = false`

			`def change`
			`remove_column :users, :external_email, :boolean`
			`end`
			`end`