[
https://issues.apache.org/jira/browse/CALCITE-208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797329#comment-17797329
]
Mihai Budiu commented on CALCITE-208:
-------------------------------------
I will change the type names in the PR.
Regarding this question:
{color:#242424}> I have a feeling that in order to support TIMESTAMP_TZ and
TIME_TZ we will need a notion of the ‘current session time zone’. Can you check
whether we have adequate support for that? If not, it could be a separate
task.{color}
{color:#242424}I believe that the existing TIME_WITH_LOCAL_TIME_ZONE, which
seems to be already supported by Calcite, already uses the current session time
zone in its implementation. {color}
{color:#242424}This type already exists and I don't plan to rename it. (There's
also a corresponding TIMESTAMP_WITH_LOCAL_TIME_ZONE).{color}
> Support TIMESTAMP WITH TIME ZONE data type
> ------------------------------------------
>
> Key: CALCITE-208
> URL: https://issues.apache.org/jira/browse/CALCITE-208
> Project: Calcite
> Issue Type: Improvement
> Reporter: GitHub Import
> Priority: Major
> Labels: github-import
>
> Most databases have a data type that store a date + time component and a time
> zone component. It would be useful for Drill to support this data type.
> ---------------- Imported from GitHub ----------------
> Url: https://github.com/julianhyde/optiq/issues/208
> Created by: [mehant|https://github.com/mehant]
> Labels: enhancement,
> Created at: Tue Mar 25 16:57:56 CET 2014
> State: open
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
