[
https://issues.apache.org/jira/browse/CALCITE-6572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17881020#comment-17881020
]
Julian Hyde edited comment on CALCITE-6572 at 9/11/24 5:33 PM:
---------------------------------------------------------------
I agree. We generally test each function with null values. Not sure why this
didn’t happen for TO_CHAR.
TO_CHAR should return null if and only if any argument is null, therefore
should be nullable if one or more arguments are nullable. Can you change the
summary?
was (Author: julianhyde):
I agree. We generally test each function with null values. Not sure why this
didn’t happen for TO_CHAR.
> Calcite TO_CHAR function is incorrectly marked as returning a non-nullable
> result
> ---------------------------------------------------------------------------------
>
> Key: CALCITE-6572
> URL: https://issues.apache.org/jira/browse/CALCITE-6572
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.37.0
> Reporter: Claude Brisson
> Priority: Minor
>
> We would expect the result of TO_CHAR(<date or timestamp>, <format>) to be
> nullable, while it is not for now.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
