[
https://issues.apache.org/jira/browse/CALCITE-1947?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129664#comment-16129664
]
Jesus Camacho Rodriguez commented on CALCITE-1947:
--------------------------------------------------
Thanks for the quick feedback [~julianhyde].
Indeed this implementation is not consistent with the standard. However,
{{TIMESTAMP WITH LOCAL TIME ZONE}} seems to have similar semantics to Postgres
indeed, thus it seems a proper name for the type. I will check it into more
detail and change the name accordingly.
I will also refactor TimestampString / TimestampWithTimeZoneString and update
the PR.
> Add time/timestamp with time zone types to optimizer
> ----------------------------------------------------
>
> Key: CALCITE-1947
> URL: https://issues.apache.org/jira/browse/CALCITE-1947
> Project: Calcite
> Issue Type: New Feature
> Components: core
> Reporter: Jesus Camacho Rodriguez
> Assignee: Jesus Camacho Rodriguez
> Fix For: 1.14.0
>
>
> Implementation would be similar to PostgreSQL (the {{time/timestamp with
> timezone}} types do not store the timezone) and conversion from/to
> timezone-less types follows similar semantics.
> https://www.postgresql.org/docs/9.6/static/functions-datetime.html
> This would also allow us to integrate easily with Hive and Druid, which
> follow similar storage models/semantics for timestamp with timezone.
> Follow-up work will be needed to introduce these new types in Avatica and
> extend Calcite SQL parser.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
