-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[bug](prepared statement) fix double type value incorrect in legacy planner #36704
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
[bug](prepared statement) fix double type value incorrect in legacy planner #36704
Conversation
|
run buildall |
|
Thank you for your contribution to Apache Doris. Since 2024-03-18, the Document has been moved to doris-website. |
TPC-H: Total hot run time: 39782 ms |
TPC-DS: Total hot run time: 174591 ms |
ClickBench: Total hot run time: 30.96 s |
| break; | ||
| case 5: // MYSQL_TYPE_DOUBLE | ||
| literalExpr = LiteralExpr.create("0", Type.DOUBLE); | ||
| literalExpr.setType(Type.DOUBLE); |
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.
if double should set it type, should we just change DOUBLE branch in LiteralExpr::create?
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.
LiteralExpr::create is used in many places, it's best not to change it.
lide-reed
left a comment
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
|
PR approved by at least one committer and no changes requested. |
|
PR approved by anyone and no changes requested. |
…lanner (#36704) ## Proposed changes fix double type value incorrect. <!--Describe your changes.-->
Proposed changes
Issue Number: close #xxx
fix double type value incorrect.