[
https://issues.apache.org/jira/browse/CALCITE-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17939754#comment-17939754
]
Guillaume Massé commented on CALCITE-6275:
------------------------------------------
here is a few example where it would be useful:
array in snowflake:
[https://docs.snowflake.com/en/sql-reference/data-types-structured#specifying-a-structured-array-type]
value type of map in snowflake:
[https://docs.snowflake.com/en/sql-reference/data-types-structured#label-structured-types-specifying-map]
row type in snowflake:
[https://docs.snowflake.com/en/sql-reference/data-types-structured#label-structured-types-specifying-object]
and in spark:
[https://docs.databricks.com/aws/en/sql/language-manual/data-types/struct-type]
In our close source code base, we added dataTypeParserMethods and
custom/extended dialects to support those cases.
> Parser for data types ignores element nullability in collections
> ----------------------------------------------------------------
>
> Key: CALCITE-6275
> URL: https://issues.apache.org/jira/browse/CALCITE-6275
> Project: Calcite
> Issue Type: Bug
> Components: core, server
> Affects Versions: 1.36.0
> Reporter: Mihai Budiu
> Priority: Major
> Labels: pull-request-available
>
> The parser (Parser.jj) has this production rule for DataType:
> {code}
> // Type name with optional scale and precision.
> SqlDataTypeSpec DataType() :
> {
> SqlTypeNameSpec typeName;
> final Span s;
> }
> {
> typeName = TypeName() {
> s = Span.of(typeName.getParserPos());
> }
> (
> typeName = CollectionsTypeName(typeName)
> )*
> {
> return new SqlDataTypeSpec(typeName,
> s.add(typeName.getParserPos()).pos());
> }
> }
> {code}
> Note that there is no way to specify the nullability for the elements of a
> collection, they are always assumed to be non-null. This is most pertinent
> for the server component, where in DDL one cannot specify a table column of
> type INTEGER ARRAY; one always gets an INTEGER NOT NULL ARRAY instead.
> But note that SqlCollectionTypeNameSpec cannot even represent the nullability
> of the elements' type, it takes a SqlTypeNameSpec instead of a
> SqlDataTypeSpec.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)