0fc9f9d3e7
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
15 lines
510 B
Ruby
15 lines
510 B
Ruby
class CreateProjectAuthorizations < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :project_authorizations do |t|
|
|
t.references :user, foreign_key: { on_delete: :cascade }
|
|
t.references :project, foreign_key: { on_delete: :cascade }
|
|
t.integer :access_level
|
|
|
|
t.index [:user_id, :project_id, :access_level], unique: true, name: 'index_project_authorizations_on_user_id_project_id_access_level'
|
|
end
|
|
end
|
|
end
|