-
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,planner: fix to preserve the precision information of a timestamp-typed column in the plan cache #8619
Conversation
Hi contributor, thanks for your PR. This patch needs to be approved by someone of admins. They should reply with "/ok-to-test" to accept this PR for running test automatically. |
/run-all-tests |
/run-common-test |
1 similar comment
/run-common-test |
/run-all-tests |
/run-common-test |
/run-all-tests |
/run-unit-test |
/run-sqllogic-test |
/run-all-tests |
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 |
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
@dbjoa Could you please help us cherry-pick this commit to release-2.1 and release-2.0? |
…mestamp-typed column in the plan cache (pingcap#8619)
…ldType.Clone() (pingcap#8641)
…one() member function (pingcap#77)
…one() member function (pingcap#77)
What problem does this PR solve?
Fix #8615
What is changed and how it works?
When cloning
FieldType.Tp
from the source,FieldType.Decimal
should be cloned too because it can be used asFsp
inTimestamp
type.Check List
Tests
Code changes
Side effects
Related changes
This change is