[
https://issues.apache.org/jira/browse/CALCITE-6707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901626#comment-17901626
]
xiong duan commented on CALCITE-6707:
-------------------------------------
[~mbudiu]
If we check the NULL type when the check the return value is NULL, we can see
that many operators have the same problem.
Enrich the testing strategy for SQLOperatorFixtureImpl#checkNULL
{code:java}
@Override public void checkNull(String expression) {
tester.forEachQuery(factory, expression, sql ->
tester.check(factory, sql, SqlTests.ANY_TYPE_CHECKER, isNullValue()));
checkType(expression, "NULL");
}{code}
> Type inference for CHR function is wrong
> ----------------------------------------
>
> Key: CALCITE-6707
> URL: https://issues.apache.org/jira/browse/CALCITE-6707
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.38.0
> Reporter: Mihai Budiu
> Assignee: Mihai Budiu
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.39.0
>
>
> The return type of CHR is always CHAR(1), and never nullable.
> However, if the argument of CHR is nullable, the result should be nullable as
> well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
