[
https://issues.apache.org/jira/browse/CALCITE-6932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939747#comment-17939747
]
Mihai Budiu commented on CALCITE-6932:
--------------------------------------
I think this is related to https://issues.apache.org/jira/browse/CALCITE-6275
and it looks like a messy problem.
The way the nullability is handled in the parser is rather random.
For tables it's by default nullable
For ROW types it's by default non nullable
For collection types it cannot be specified at all for elements, and it's not
clear whether it's nullable or not.
> SqlTypeUtil.convertTypeToSpec discard isNullable
> ------------------------------------------------
>
> Key: CALCITE-6932
> URL: https://issues.apache.org/jira/browse/CALCITE-6932
> Project: Calcite
> Issue Type: Bug
> Reporter: Guillaume Massé
> Priority: Minor
> Labels: pull-request-available
>
> I'm writing unparse of an Array for Snowflake and I need to access the
> nullability of SqlDataTypeSpec
> [https://docs.snowflake.com/en/sql-reference/data-types-structured#specifying-a-structured-array-type]
> I was using org.apache.calcite.sql.type.SqlTypeUtil.convertTypeToSpec and
> noticed it's not using type.isNullable()
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
