[
https://issues.apache.org/jira/browse/CALCITE-3213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16910624#comment-16910624
]
Julian Hyde commented on CALCITE-3213:
--------------------------------------
Sounds like a good list, and it will be a major improvement that complex types
are treated as first class objects.
Minor point, but whenever you can, describe a change in terms of its SQL
syntax. (When you talk about "SqlDataTypeSpec" you are narrowing the audience
to people who actually write Calcite code or use its APIs, but everyone
understands what you mean when you use SQL.) Also, capitalize the SQL keywords.
Here's my attempt to re-work your list. Please correct any inaccuracies.
* Anonymous type based on ROW
* Anonymous type based on ARRAY
* Anonymous type based on nested collection (ARRAY and MULTISET)
* In TIME and TIMESTAMP types, allow WITH TIME ZONE and WITH LOCAL TIME ZONE
variants
* Allow collection type (ARRAY and MULTISET) and NOT NULL in CREATE TYPE
> Support complex type expressions for SqlDataTypeSpec
> -----------------------------------------------------
>
> Key: CALCITE-3213
> URL: https://issues.apache.org/jira/browse/CALCITE-3213
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.20.0
> Reporter: Danny Chan
> Assignee: Danny Chan
> Priority: Major
> Fix For: 1.21.0
>
>
> We should support nested struct type like:
> {code:sql}
> ROW(
> foo NUMBER(5, 2) NOT NULL,
> rec ROW(b BOOLEAN, i MyUDT NOT NULL))
> {code}
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
