[
https://issues.apache.org/jira/browse/CALCITE-5500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde resolved CALCITE-5500.
----------------------------------
Fix Version/s: 1.33.0
Resolution: Duplicate
> Add support in Avatica for TIMESTAMP WITH LOCAL TIME ZONE
> ---------------------------------------------------------
>
> Key: CALCITE-5500
> URL: https://issues.apache.org/jira/browse/CALCITE-5500
> Project: Calcite
> Issue Type: Improvement
> Components: avatica
> Reporter: Will Noble
> Priority: Major
> Fix For: 1.33.0
>
>
> This is closely related to CALCITE-5446 but tracks the changes required in
> Avatica. This is where time zone conversion happens when the client invokes a
> getter method on a {{ResultSet}}. Here are the intended semantics for
> {{TIMESTAMP}} and {{TIMESTAMP WITH LOCAL TIME ZONE}}:
> {{TIMESTAMP}}:
> * {{getString()}} -> Always returns the same string no matter the client's
> time zone
> * {{getTimestamp()}} -> Subtracts the zone offset from the instant, so
> rendering the instant to a string in the client's time zone produces the same
> result as {{getString()}}
> {{TIMESTAMP WITH LOCAL TIME ZONE}}:
> * {{getTimestamp()}} -> Always returns the same instant no matter the time
> zone
> * {{getString()}} -> Adds the zone offset to the instant before rending it to
> a string, so rendering the result of {{getTimestamp()}} in the client's time
> zone produces the same result as this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
