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
25 lines
878 B
Ruby
25 lines
878 B
Ruby
class FixDevTimezoneSchema < ActiveRecord::Migration[4.2]
|
|
include Gitlab::Database::MigrationHelpers
|
|
|
|
# The this migrations tries to help solve unwanted changes to `schema.rb`
|
|
# while developing GitLab. Installations created before we started using
|
|
# `datetime_with_timezone` are likely to face this problem. Updating those
|
|
# columns to the new type should help fix this.
|
|
|
|
# Set this constant to true if this migration requires downtime.
|
|
DOWNTIME = false
|
|
|
|
TIMEZONE_TABLES = %i(appearances ci_group_variables ci_pipeline_schedule_variables events gpg_keys gpg_signatures project_auto_devops)
|
|
|
|
def up
|
|
return unless Rails.env.development? || Rails.env.test?
|
|
|
|
TIMEZONE_TABLES.each do |table|
|
|
change_column table, :created_at, :datetime_with_timezone
|
|
change_column table, :updated_at, :datetime_with_timezone
|
|
end
|
|
end
|
|
|
|
def down
|
|
end
|
|
end
|