engine/schema: add empty DB upgrade path from 4.15.0.0 to 4.16.0.0 #4506
Conversation
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
davidjumani
requested review from
shwstppr and
yadvr
and removed request for
shwstppr
davidjumani
force-pushed
the
416-upgrade-path
branch
from
632a6fe to
b83e2fe
Compare
Member
|
@davidjumani I've handled this to resolve db path conflicts from 4.14->4.15-> master branch. The fwd merged on master branch has handled all the path. I'll close the PR, pl open another PR for any new/additional changes. Thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Description
Empty DB upgrade path from 4.15.0.0 to 4.16.0.0
Types of changes
How Has This Been Tested?