-
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
expression: fix the wrong behavior of conv
function (#53681)
#56889
expression: fix the wrong behavior of conv
function (#53681)
#56889
Conversation
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: hawkingrei, qw4990 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
[LGTM Timeline notifier]Timeline:
|
/test unit-test |
@qw4990: No presubmit jobs available for pingcap/tidb@release-7.1 In response to this:
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 kubernetes-sigs/prow repository. |
/test unit-test |
@qw4990: No presubmit jobs available for pingcap/tidb@release-7.1 In response to this:
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 kubernetes-sigs/prow repository. |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## release-7.1 #56889 +/- ##
================================================
Coverage ? 73.4805%
================================================
Files ? 1212
Lines ? 381316
Branches ? 0
================================================
Hits ? 280193
Misses ? 83227
Partials ? 17896 |
This is an automated cherry-pick of #53681
What problem does this PR solve?
Issue Number: close #53505
Problem Summary: expression: fix the wrong behavior of
conv
functionWhat changed and how does it work?
When evaluating
Constant
, should always useConstant.EvalXXX()
instead of accessingConstant.Value
directly, otherwise there might be wrong result if it's a parameter (?
).Check List
Tests
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.