-
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
executor: refineArgs() bug fix when compare int with very small decimal (#23694) #23705
executor: refineArgs() bug fix when compare int with very small decimal (#23694) #23705
Conversation
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
Signed-off-by: guo-shaoge <shaoge1994@163.com>
/run-all-tests |
@lzmhhh123 you're already a collaborator in bot's repo. |
/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 |
/merge |
@ti-srebot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
/merge |
/merge cancel |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: d1274ef
|
cherry-pick #23694 to release-4.0
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/23705
After apply modifications, you can push your change to this PR via:
Signed-off-by: guo-shaoge shaoge1994@163.com
What problem does this PR solve?
Issue Number:
close #23623
close #23684
Problem Summary: In the following case, output of select stmt should be 2, but current result is 3.
Why: c1 is nullable, so we cannot assuse all value in c1 will be greater than the result of subquery, which is less than int32_min. Because result of
null > xxx
is NULLWhat is changed and how it works?
What's Changed: when
refineArgs()
, should check if column is nullable. If is nullable, we should not try to optimize compare expression.Related changes
Check List
Tests
Side effects
Release note