fix: correct oracle and postgres schema versions when bootstrapped #6779
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
Signed-off-by: Chad Wilson <[email protected]>
jeremylong
approved these changes
Jul 3, 2024
|
again - thank you for the PR. I really need to setup automated testing for the database integrations.... |
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 Issue
Noted by users at #6746 (comment) and #6746 (comment) for Postgres, but likely missed due to the many other unrelated comments. Similar oversight exists for Oracle, but not sure if there are other issues there as imagine oracle is less frequently used.
Description of Change
No idea if the rest of the changes actually work, but these version numbers seem definitely wrong, and would need to an attempt to re-run delta scripts later?
Have test cases been added to cover the new functionality?
no