[
https://issues.apache.org/jira/browse/CALCITE-3238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17147274#comment-17147274
]
Jiaming Xie commented on CALCITE-3238:
--------------------------------------
[~danny0405] In this PR, many fields of SqlDataTypeSpec are removed(e.g. scale,
precision, charSetName). I am not able to figure out whether the fields are
moved to some other class to hold, or the fields are useless so they are simply
deleted. Could you kindly provide some explanation here?
Besides, if I want to roll the calcite-based projects (e.g. flink) to depend on
the new version of calcite (e.g. from 1.20 to 1.23 for flink), as the fields
are removed, what should I do to safely integrated with the new simplified
SqlDataTypeSpec of calcite?
> Support Time Zone suffix of DateTime types for SqlDataTypeSpec
> --------------------------------------------------------------
>
> Key: CALCITE-3238
> URL: https://issues.apache.org/jira/browse/CALCITE-3238
> Project: Calcite
> Issue Type: Sub-task
> Components: core
> Affects Versions: 1.20.0
> Reporter: Danny Chen
> Assignee: Danny Chen
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.21.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> This is the grammar copied from SQL-2011:
> {code:sql}
> <datetime type> ::=
> DATE
> | TIME [ <left paren> <time precision> <right paren> ] [ <with or without
> time zone> ]
> | TIMESTAMP [ <left paren> <timestamp precision> <right paren> ]
> [ <with or without time zone> ]
> <with or without time zone> ::=
> WITH TIME ZONE
> | WITHOUT TIME ZONE
> <time precision> ::=
> <time fractional seconds precision>
> <timestamp precision> ::=
> <time fractional seconds precision>
> <time fractional seconds precision> ::=
> <unsigned integer>
> {code}
> We extend this grammar to support "with local time zone" definition:
> {code:sql}
> time(0) with local time zone
> timestamp(0) with local time zone
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
