You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@calcite.apache.org by "Will Noble (Jira)" <ji...@apache.org> on 2021/11/02 15:52:00 UTC

[jira] [Updated] (CALCITE-4872) UNKNOWN SqlTypeName erroneously treated as NULL

     [ https://issues.apache.org/jira/browse/CALCITE-4872?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Will Noble updated CALCITE-4872:
--------------------------------
    Summary: UNKNOWN SqlTypeName erroneously treated as NULL  (was: UNKNOWN erroneously treated as NULL)

> UNKNOWN SqlTypeName erroneously treated as NULL
> -----------------------------------------------
>
>                 Key: CALCITE-4872
>                 URL: https://issues.apache.org/jira/browse/CALCITE-4872
>             Project: Calcite
>          Issue Type: Bug
>          Components: core
>            Reporter: Will Noble
>            Assignee: Will Noble
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Call {{createWithNullability}} on an {{UnknownSqlType}} currently returns a {{NULL}} type. Furthermore, it's impossible to cast to unknown types, according to {{SqlTypeUtil.canCastFrom}}. This introduces a new {{SqlTypeName}} -- {{UNKNOWN}} -- which behaves like {{NULL}} in all ways except that it's no longer actually equal to {{NULL}}, and can always be cast to.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)