-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
fix: coalesce function should return correct data type #9459
Conversation
Some remaining test failures are unrelated. But some seem related. I'll keep looking into them. |
if *type_into == coerced_type { | ||
Some(coerced_type) | ||
} else { |
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.
For function argument, we want to coerce to exact the type (valid type) instead of third type.
"could not cast {} from {} to {}", | ||
$NAME, | ||
$ARG.data_type(), | ||
type_name::<$ARRAY_TYPE>() | ||
)) |
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.
When I debug, I found that it is a more useful error message to show the source data type too.
Thanks @Dandandan |
* fix: Remove supported coalesce types * Use comparison_coercion * Fix test * Fix * Add comment * More * fix
Which issue does this PR close?
Closes #9458.
Rationale for this change
What changes are included in this PR?
Are these changes tested?
Are there any user-facing changes?