[14.0][FIX] detect if we have edi_oca from v12 already - #4384
Merged
Conversation
hbrunn
force-pushed
the
14.0-handle-edi_oca
branch
from
April 8, 2024 06:00
b1b3fe8 to
6674058
Compare
Contributor
|
Hi @StefanRijnhart, @MiquelRForgeFlow, @pedrobaeza, |
pedrobaeza
approved these changes
Apr 8, 2024
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
edi_ocahas been merged into v12, but doesn't exist in v13. So when migrating from a v12 database, the rename fails.On the other hand, when migrating from a v13 database, we want the rename.