gitlab-org--gitlab-foss/db/migrate/20160516174813_add_send_use...

# rubocop:disable all
class AddSendUserConfirmationEmailToApplicationSettings < ActiveRecord::Migration[4.2]
  def up
    add_column :application_settings, :send_user_confirmation_email, :boolean, default: false

    #Sets confirmation email to true by default on existing installations.
    execute "UPDATE application_settings SET send_user_confirmation_email=true"
  end

  def down
    remove_column :application_settings, :send_user_confirmation_email
  end
end
Enable RuboCop for migrations Migrations shouldn't fail RuboCop checks - especially lint checks, such as the nested method check. To avoid changing code in existing migrations, add the magic comment to the top of each of them to skip that file. 2016-06-09 12:39:16 +00:00			`# rubocop:disable all`
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 AddSendUserConfirmationEmailToApplicationSettings < ActiveRecord::Migration[4.2]`
Change skip_user_confirmation_email to send_user_confirmation_email 2016-04-28 20:09:15 +00:00			`def up`
			`add_column :application_settings, :send_user_confirmation_email, :boolean, default: false`

			`#Sets confirmation email to true by default on existing installations.`
Change landing page when skipping confirmation email and add documentation 2016-05-06 20:59:45 +00:00			`execute "UPDATE application_settings SET send_user_confirmation_email=true"`
Change skip_user_confirmation_email to send_user_confirmation_email 2016-04-28 20:09:15 +00:00			`end`

			`def down`
			`remove_column :application_settings, :send_user_confirmation_email`
			`end`
			`end`