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
23 lines
700 B
Ruby
23 lines
700 B
Ruby
# See http://doc.gitlab.com/ce/development/migration_style_guide.html
|
|
# for more information on how to write migrations for GitLab.
|
|
|
|
class CreateClustersApplicationsJupyter < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :clusters_applications_jupyter do |t|
|
|
t.references :cluster, null: false, unique: true, foreign_key: { on_delete: :cascade }
|
|
t.references :oauth_application, foreign_key: { on_delete: :nullify }
|
|
|
|
t.integer :status, null: false
|
|
t.string :version, null: false
|
|
t.string :hostname
|
|
|
|
t.timestamps_with_timezone null: false
|
|
|
|
t.text :status_reason
|
|
end
|
|
end
|
|
end
|