executor: Fix a bug in 'INSERT ... ON DUPLICATE KEY UPDATE' #7675
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.
What problem does this PR solve?
Fix a bug in 'INSERT ... ON DUPLICATE KEY UPDATE' when unique key are updated, for example:
, which is incorrect. We should expect the following result instead:
After this PR, it will be fixed.
What is changed and how it works?
In
InsertExec
'supdateDupKeyValues
function,dupKVs
(amap
that holds existing primary keys and unique keys for duplication detection) is updated by removing keys from the inserting row first, then adding keys from the updated row. But we should remove keys from the old row instead, because old row is the one that to be replaced.Check List
Tests
Code changes
Side effects
Related changes