kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/db/migrate/20160212123307_create_tasks.rb

18 lines
486 B
Ruby
Raw Normal View History

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 CreateTasks < ActiveRecord::Migration[4.2]
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
Add task model
2016-02-12 13:17:42 +00:00
def change
create_table :tasks do |t|
t.references :user, null: false, index: true
t.references :project, null: false, index: true
t.references :target, polymorphic: true, null: false, index: true
t.integer :author_id, index: true
t.integer :action, null: false
t.string :state, null: false, index: true
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
Add task model
2016-02-12 13:17:42 +00:00
end
end
end