gitlab-org--gitlab-foss/db/migrate/20131112114325_create_broad...

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

  def change
    create_table :broadcast_messages do |t|
      t.text :message, null: false
      t.datetime :starts_at
      t.datetime :ends_at
      t.integer :alert_type

      t.timestamps null: true
    end
  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`
Broadcast message model + migrations Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2013-11-12 11:47:28 +00:00			`class CreateBroadcastMessages < ActiveRecord::Migration`
Make the downtime_check task happy Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-11-30 15:15:02 +00:00			`DOWNTIME = false`

Broadcast message model + migrations Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2013-11-12 11:47:28 +00:00			`def change`
			`create_table :broadcast_messages do \|t\|`
			`t.text :message, null: false`
			`t.datetime :starts_at`
			`t.datetime :ends_at`
			`t.integer :alert_type`

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 15:45:08 +00:00			`t.timestamps null: true`
Broadcast message model + migrations Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2013-11-12 11:47:28 +00:00			`end`
			`end`
			`end`