gitlab-org--gitlab-foss/db/migrate/20140209025651_create_emails.rb

# rubocop:disable all
class CreateEmails < ActiveRecord::Migration
  DOWNTIME = false

  def change
    create_table :emails do |t|
      t.integer  :user_id, null: false
      t.string   :email, null: false

      t.timestamps null: true
    end

    add_index :emails, :user_id
    add_index :emails, :email, unique: true
  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 08:39:16 -04:00			`# rubocop:disable all`
Add email aliases for users Emails are used to associate commits with users. The emails are not verified and don't have to be valid email addresses. They are assigned on a first come, first serve basis. Notifications are sent when an email is added. 2014-02-08 22:08:49 -05:00			`class CreateEmails < ActiveRecord::Migration`
Make the downtime_check task happy Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-30 10:15:02 -05:00			`DOWNTIME = false`

Add email aliases for users Emails are used to associate commits with users. The emails are not verified and don't have to be valid email addresses. They are assigned on a first come, first serve basis. Notifications are sent when an email is added. 2014-02-08 22:08:49 -05:00			`def change`
			`create_table :emails do \|t\|`
			`t.integer :user_id, null: false`
			`t.string :email, null: false`
Make the downtime_check task happy Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-30 10:15:02 -05:00
Add `null: true` to timestamps in migrations that does not define it This is to ensure that migrations will still be consitent when we will upgrade to Rails 5 which default to `null: false` for timestamps columns. Fixes #23666. Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-28 10:45:08 -05:00			`t.timestamps null: true`
Add email aliases for users Emails are used to associate commits with users. The emails are not verified and don't have to be valid email addresses. They are assigned on a first come, first serve basis. Notifications are sent when an email is added. 2014-02-08 22:08:49 -05:00			`end`

			`add_index :emails, :user_id`
			`add_index :emails, :email, unique: true`
			`end`
			`end`