gitlab-org--gitlab-foss/db/migrate/20160831214002_create_proje...

# rubocop:disable Migration/Timestamps
class CreateProjectFeatures < ActiveRecord::Migration[4.2]
  DOWNTIME = false

  def change
    create_table :project_features do |t|
      t.belongs_to :project, index: true
      t.integer  :merge_requests_access_level
      t.integer  :issues_access_level
      t.integer  :wiki_access_level
      t.integer  :snippets_access_level
      t.integer  :builds_access_level

      t.timestamps null: true
    end
  end
end
Add database helpers 'add_timestamps_with_timezone' and 'timestamps_with_timezone' 2017-06-13 11:44:13 +00:00			`# rubocop:disable Migration/Timestamps`
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 CreateProjectFeatures < ActiveRecord::Migration[4.2]`
Project tools visibility level 2016-08-01 22:31:21 +00:00			`DOWNTIME = false`

			`def change`
			`create_table :project_features do \|t\|`
			`t.belongs_to :project, index: true`
			`t.integer :merge_requests_access_level`
			`t.integer :issues_access_level`
			`t.integer :wiki_access_level`
			`t.integer :snippets_access_level`
			`t.integer :builds_access_level`

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`
Project tools visibility level 2016-08-01 22:31:21 +00:00			`end`
			`end`
			`end`