test(#454): add test for improper conflict resolution#477
Closed
PadenZach wants to merge 1 commit into
Closed
Conversation
These tests demonstrate how the current conflict building mechanism can fail if a postgres table has had columns dropped or reordered in certain ways. As described in duckdb#454
Member
|
Closing in favour of #523 |
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
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.
WIP
These tests demonstrate how the current conflict building mechanism can fail if a postgres table has had columns dropped or reordered in certain ways. As described in #454
Will follow up with fix once I sit down and dig into the problem and possible fixes a bit more.