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
16 lines
520 B
Ruby
16 lines
520 B
Ruby
class CreateProjectDeployTokens < ActiveRecord::Migration[4.2]
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :project_deploy_tokens do |t|
|
|
t.integer :project_id, null: false
|
|
t.integer :deploy_token_id, null: false
|
|
t.datetime_with_timezone :created_at, null: false
|
|
|
|
t.foreign_key :deploy_tokens, column: :deploy_token_id, on_delete: :cascade
|
|
t.foreign_key :projects, column: :project_id, on_delete: :cascade
|
|
|
|
t.index [:project_id, :deploy_token_id], unique: true
|
|
end
|
|
end
|
|
end
|