-
Notifications
You must be signed in to change notification settings - Fork 2.5k
[CALCITE-7607] DML type coercion inserts implicit narrowing casts for target-column assignments #5041
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
base: main
Are you sure you want to change the base?
[CALCITE-7607] DML type coercion inserts implicit narrowing casts for target-column assignments #5041
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -5972,7 +5972,7 @@ private void checkEmptyJoin(RelOptFixture f) { | |
| @Test void testReduceCastsNullable() { | ||
| HepProgram program = new HepProgramBuilder() | ||
|
|
||
| // Simulate the way INSERT will insert casts to the target types | ||
| // Simulate the way INSERT can insert casts to the target types. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't understand why this comment needs to be changed.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I changed it because |
||
| .addRuleInstance( | ||
| CoerceInputsRule.Config.DEFAULT | ||
| .withCoerceNames(false) | ||
|
|
||
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.
These variations in precision may also require an explanation.
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.
The original SQL uses
123.4. The old plan cast the value through a narrower floating-point type, which produced123.4000015258789E0; without that cast the value stays123.4.