[
https://issues.apache.org/jira/browse/CALCITE-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759225#comment-17759225
]
hongyu guo commented on CALCITE-5956:
-------------------------------------
Hi, [~julianhyde], thank you for your comment.
I will present my ideas for this case in two ways:
- The SQL standard syntax cannot represent MAP types, so implementing dialects
similar to {{ARRAY<T>}} can better support {{MAP<K, V>}} syntax in the future.
(As discussed in CALCITE-5570)
- I think this is compatible with a grammar, which does not have a destructive
effect on Calcite, but rather enhances it.
> Support parsing non-standard collection types
> ---------------------------------------------
>
> Key: CALCITE-5956
> URL: https://issues.apache.org/jira/browse/CALCITE-5956
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Affects Versions: 1.35.0
> Reporter: hongyu guo
> Assignee: hongyu guo
> Priority: Major
> Fix For: 1.36.0
>
>
> Calcite support SQL standard collection types. For example:
> {code:sql}
> INTEGER ARRAY;
> INTEGER ARRAY ARRAY;
> VARCHAR(5) MULTISET;
> INTEGER MULTISET ARRAY;{code}
> Many DBMS support a dialect of {{ARRAY<T>}} and {{MULITSET<T>}},
> I think Calcite can also support this dialect in core Parser.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
