Refactor #21100

Explicitly set DB migration compatibility to 4.2
Related issues
Associated revisions
History
#1
Updated by Anonymous over 5 years ago
- Related to Tracker #15715: Rails 5.0 upgrade tasks added
#2
Updated by Anonymous over 5 years ago
- Blocks Tracker #20948: Rails 5.1 upgrade tasks added
#3
Updated by Anonymous over 5 years ago
- Blocked by Refactor #21084: Always use Rails 5.0, Drop Rails 4.2 added
#4
Updated by The Foreman Bot over 5 years ago
- Status changed from Assigned to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/5020 added
#5
Updated by Dominic Cleal over 5 years ago
- % Done changed from 0 to 100
- Status changed from Ready For Testing to Closed
Applied in changeset bc038098bc2f96986442ae2fffac4e4746933cec.
Fixes #21100 - set DB migration compatibility to 4.2
Put all existing DB migrations into 4.2 compatibility mode as they don't
specify null => true on timestamp columns etc.