Fix issue with migration from 8 and added support for 8.18 migration #12020
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…s changed in 9.3, but added in 9.0. we need to use the legacy models when running 9.0 migrations
nikolajlauridsen
approved these changes
Feb 17, 2022
nikolajlauridsen
deleted the
v9/hotfix/fix_issue_with_migration_from_8_and_added_support_for_8.18_migration
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #11976
Fix issue with migration from 8 and added support for 8.18 migration.
The 8.18 have added a new noop migration (8ff1d49) just to change state, so we can but it into the right order in v9. Otherwise it would skip directly to 9.1 and continue from there.
The bug was fixed by reintoducting the old model from pre 9.3, and only use it for the old migrations