[
https://issues.apache.org/jira/browse/CALCITE-5956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17759955#comment-17759955
]
hongyu guo commented on CALCITE-5956:
-------------------------------------
[~julianhyde], I think use "<>" or "()" is not a big problem, dialect can help
us convert to appropriate syntax when user connect to different DBMS.
I +1 for "MAP<K, V>".
Another question: Should we add {{ARRAY<T>}} and {{MULTISET<T>}} to core Parser?
* Add to core: build a stronger parser, and better support {{MAP<K, V>}} in
the future (my opinion)
* Add to babel: core parser is too heavy. ([~jiajunbernoulli]'s opinion)
I want to do some work for parsing {{ARRAY<T>}} and {{MULTISET<T>}} first after
we make a decision:)
> 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)
