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.
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
executor: change the evaluation order of columns in
Update
andInsert
statements #57123executor: change the evaluation order of columns in
Update
andInsert
statements #57123Changes from 2 commits
9381a49
befa301
80aab91
8f7117d
cbe3925
3d8a2b4
484291b
f655f8f
69a7c1b
ac898c6
af6b478
93c6d69
0ba873c
12a3f93
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
It only fixes the
INSERT .. ON DUPLICATE UPDATE ..
case. As I have tested, theUPDATE
path also has the same bug:Then the following two queries will have different result:
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.
Is it possible to move the logic of handling generated column into the
updateRecord
? It seems that the functionupdateRecord
also handles theON UPDATE
columns (and as we specified allON UPDATE
column in this functioin, these logic are meaningless).Another possible solution is to remove the codes related to
ON UPDATE
columns inupdateRecord
function. However, as the same logic will be used multiple times (inINSERT .. ON DUPLICATE UPDATE
and a normalUPDATE
statement), I prefer to write the codes related to generated column inupdateRecord
to avoid repeating the codes.