[
https://issues.apache.org/jira/browse/ARROW-637?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15930725#comment-15930725
]
Julian Hyde commented on ARROW-637:
-----------------------------------
[~grahn], I know that PostgreSQL's "timestamp with time zone" is basically an
"instant". Thanks for confirming.
It wasn't clear in your comment whether Oracle does the correct thing (per the
SQL standard) and stores a time zone value. Can you clarify?
As far as I know Teradata and DB2 do the right thing. And I don't know of any
other DBs that support it.
As an aside: my biggest gripe with PostgreSQL is that they called their type
"TIMESTAMP WITH TIME ZONE". Their type is a useful one to have in any DBMS,
since it matches what C/UNIX and Java developers are used to. I just wish
they'd called it "INSTANT".
> [Format] Add time zone metadata to Timestamp type
> -------------------------------------------------
>
> Key: ARROW-637
> URL: https://issues.apache.org/jira/browse/ARROW-637
> Project: Apache Arrow
> Issue Type: New Feature
> Components: Format
> Reporter: Wes McKinney
> Assignee: Wes McKinney
>
> As a metadata-only convenience, it would be useful to have an optional Olson
> time zone name or absolute time offset (e.g. {{+07:30}}) in the {{Timestamp}}
> flatbuffers type:
> https://github.com/apache/arrow/blob/master/format/Message.fbs#L94
> Null or length-0 string would indicate that the data is time zone naive, and
> shall not be considered to be localized.
> https://github.com/apache/arrow/pull/388
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
