diff options
| author | Jan Provaznik <jprovaznik@gitlab.com> | 2018-11-13 10:27:31 +0300 |
|---|---|---|
| committer | Jan Provaznik <jprovaznik@gitlab.com> | 2018-11-22 15:18:28 +0300 |
| commit | 0fc9f9d3e741629987afd2370069485bca640396 (patch) | |
| tree | dfa0f6609bd5cb66dd83789c671919f80c2bc8a1 /db/migrate/20180330121048_add_issue_due_to_notification_settings.rb | |
| parent | fcec474ceb7d4f7d715ef39cbfee6936b52254f7 (diff) | |
Add version 4.2 to all existing 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/migrate/20180330121048_add_issue_due_to_notification_settings.rb')
| -rw-r--r-- | db/migrate/20180330121048_add_issue_due_to_notification_settings.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/db/migrate/20180330121048_add_issue_due_to_notification_settings.rb b/db/migrate/20180330121048_add_issue_due_to_notification_settings.rb index c64a481fcf0..2d9ca002872 100644 --- a/db/migrate/20180330121048_add_issue_due_to_notification_settings.rb +++ b/db/migrate/20180330121048_add_issue_due_to_notification_settings.rb @@ -1,4 +1,4 @@ -class AddIssueDueToNotificationSettings < ActiveRecord::Migration +class AddIssueDueToNotificationSettings < ActiveRecord::Migration[4.2] include Gitlab::Database::MigrationHelpers DOWNTIME = false |