You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@calcite.apache.org by "Will Noble (Jira)" <ji...@apache.org> on 2023/01/19 19:48:00 UTC
[jira] [Created] (CALCITE-5487) Avatica Result Sets do not properly handle TIMESTAMP WITH LOCAL TIME ZONE
Will Noble created CALCITE-5487:
-----------------------------------
Summary: Avatica Result Sets do not properly handle TIMESTAMP WITH LOCAL TIME ZONE
Key: CALCITE-5487
URL: https://issues.apache.org/jira/browse/CALCITE-5487
Project: Calcite
Issue Type: Bug
Components: avatica
Reporter: Will Noble
With the addition of proper support for {{TIMESTAMP WITH LOCAL TIME ZONE}} to Calcite being done as part of CALCITE-5346, Avatica needs to support the proper semantics for this type. Whereas a regular {{TIMESTAMP}} always has the same string representation but can have different instants depending on the calendar (time zone) passed to the result set getter, a {{TIMESTAMP WITH LOCAL TIME ZONE}} does the inverse: it always represents the same instant, but could have a different string representation depending on the calendar passed to the result set getter.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)