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
19 lines
682 B
Ruby
19 lines
682 B
Ruby
class CreateCiBuildTraceSections < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
DOWNTIME = false
|
|
|
|
def change
|
|
create_table :ci_build_trace_sections do |t|
|
|
t.references :project, null: false, index: true, foreign_key: { on_delete: :cascade }
|
|
t.datetime_with_timezone :date_start, null: false
|
|
t.datetime_with_timezone :date_end, null: false
|
|
t.integer :byte_start, limit: 8, null: false
|
|
t.integer :byte_end, limit: 8, null: false
|
|
t.integer :build_id, null: false
|
|
t.integer :section_name_id, null: false
|
|
end
|
|
|
|
add_index :ci_build_trace_sections, [:build_id, :section_name_id], unique: true
|
|
end
|
|
end
|