-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
planner: fix subquery update with generated column #23955
Conversation
/lgtm |
LGTM |
This issue does not exist on release-4.0? |
yes, it's introduced by #23404 and only affect on 5.0 |
maybe we need /lgtm 😄 |
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.
/lgtm
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by writing |
/merge |
/run-all-tests |
/merge |
/merge |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-5.0 in PR #24055 |
(cherry picked from commit 4d92261)
What problem does this PR solve?
Issue Number: close #23947
Problem Summary:
generate column will generate assign to non-updatable subquery part
What is changed and how it works?
Proposal: xxx
What's Changed, How it Works:
don't generate assign to not updatable subquery
Related changes
Check List
Tests
Side effects
Release note
This change is