diff options
author | Jan Provaznik <jprovaznik@gitlab.com> | 2018-11-13 08:27:31 +0100 |
---|---|---|
committer | Jan Provaznik <jprovaznik@gitlab.com> | 2018-11-22 13:18:28 +0100 |
commit | 0fc9f9d3e741629987afd2370069485bca640396 (patch) | |
tree | dfa0f6609bd5cb66dd83789c671919f80c2bc8a1 /db/post_migrate/20180529152628_schedule_to_archive_legacy_traces.rb | |
parent | fcec474ceb7d4f7d715ef39cbfee6936b52254f7 (diff) | |
download | gitlab-ce-0fc9f9d3e741629987afd2370069485bca640396.tar.gz |
Add version 4.2 to all existing migrationsjprovazn-versioned-migrations
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
Diffstat (limited to 'db/post_migrate/20180529152628_schedule_to_archive_legacy_traces.rb')
-rw-r--r-- | db/post_migrate/20180529152628_schedule_to_archive_legacy_traces.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/db/post_migrate/20180529152628_schedule_to_archive_legacy_traces.rb b/db/post_migrate/20180529152628_schedule_to_archive_legacy_traces.rb index 965cd3a8714..6246f6afab0 100644 --- a/db/post_migrate/20180529152628_schedule_to_archive_legacy_traces.rb +++ b/db/post_migrate/20180529152628_schedule_to_archive_legacy_traces.rb @@ -1,4 +1,4 @@ -class ScheduleToArchiveLegacyTraces < ActiveRecord::Migration +class ScheduleToArchiveLegacyTraces < ActiveRecord::Migration[4.2] include Gitlab::Database::MigrationHelpers DOWNTIME = false |