-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: insert on duplicate key update missing BindVars #14728
Merged
Merged
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
Review ChecklistHello reviewers! 👋 Please follow this checklist when reviewing this Pull Request. General
Tests
Documentation
New flags
If a workflow is added or modified:
Backward compatibility
|
0e97fa3
to
c7ee6cf
Compare
Signed-off-by: wlx5575 <[email protected]>
Signed-off-by: wlx5575 <[email protected]>
Signed-off-by: wlx5575 <[email protected]>
@wlx5575 you need to run |
Signed-off-by: wlx5575 <[email protected]>
done |
Thank you @wlx5575 for your contribution and finding and fixing the bug ❤️ |
Signed-off-by: wlx5575 <[email protected]>
harshit-gangal
approved these changes
Dec 12, 2023
frouioui
reviewed
Dec 12, 2023
utils.Exec(t, conn, "insert into t11(id, sharding_key, col1, col2, col3) values(1, 2, 'a', 1, 2)") | ||
utils.Exec(t, conn, "insert into t11(id, sharding_key, col1, col2, col3) values(1, 2, 'a', 1, 2) on duplicate key update id=10;") | ||
utils.AssertMatches(t, conn, "select id, sharding_key from t11 where id=10", "[[INT64(10) INT64(2)]]") | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
frouioui
approved these changes
Dec 12, 2023
harshit-gangal
pushed a commit
that referenced
this pull request
Dec 12, 2023
Co-authored-by: wlx5575 <[email protected]> Signed-off-by: Harshit Gangal <[email protected]>
harshit-gangal
added a commit
that referenced
this pull request
Dec 12, 2023
…14728) (#14755) Signed-off-by: Harshit Gangal <[email protected]> Co-authored-by: wlx5575 <[email protected]> Co-authored-by: wlx5575 <[email protected]> Co-authored-by: Harshit Gangal <[email protected]>
ejortegau
pushed a commit
to slackhq/vitess
that referenced
this pull request
Dec 13, 2023
Co-authored-by: wlx5575 <[email protected]>
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.
Description
"In V18, the addition of trimming bound variables during insert needs to be included for each shard in this pull request: #14064. However, the scenario of 'insert on duplicate key' has been overlooked, and the bound variables added are not included for 'on duplicate key' variables."
Related Issue(s)
Checklist
Deployment Notes