-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
expression: deduce result type for multi-argument functions like IF
wrongly in some cases
#11605
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11605 +/- ##
===========================================
Coverage 81.2608% 81.2608%
===========================================
Files 426 426
Lines 92176 92176
===========================================
Hits 74903 74903
Misses 11897 11897
Partials 5376 5376 |
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
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
/run-all-tests |
/run-all-tests |
cherry pick to release-2.1 failed |
cherry pick to release-3.0 in PR #11621 |
… wrongly in some cases (pingcap#11605)
It seems that, not for sure, we failed to cherry-pick this commit to release-2.1. Please comment '/run-cherry-picker' to try to trigger the cherry-picker if we did fail to cherry-pick this commit before. @qw4990 PTAL. |
… wrongly in some cases (pingcap#11605)
What problem does this PR solve?
Fix #11594;
When we deduce the result type for a multi-argument function like
IF
, we don't takesigned/unsigned
flag into account now;What is changed and how it works?
If anyone of these input arguments is not unsigned, we set the result type to signed.
Check List
Tests