You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Andrew Pilloud (JIRA)" <ji...@apache.org> on 2018/11/26 23:07:00 UTC
[jira] [Commented] (CALCITE-2710) Some SqlFunctions use LOCAL_TZ
constant instead of using timeZone()
[ https://issues.apache.org/jira/browse/CALCITE-2710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16699679#comment-16699679 ]
Andrew Pilloud commented on CALCITE-2710:
-----------------------------------------
I think this is just a plumbing issue, I plan to work on it shortly.
> Some SqlFunctions use LOCAL_TZ constant instead of using timeZone()
> -------------------------------------------------------------------
>
> Key: CALCITE-2710
> URL: https://issues.apache.org/jira/browse/CALCITE-2710
> Project: Calcite
> Issue Type: Bug
> Components: core
> Reporter: Andrew Pilloud
> Assignee: Julian Hyde
> Priority: Major
>
> There are several methods in SqlFunctions which use a LOCAL_TZ constant to determine the file. This constant is the default system time zone, but the local time zone can be modified on the connection. This results in incorrect behavior if the system time zone and connection time zone differ, for example adding an offset and removing a different offset. These functions should be calling the timeZone method which fetches the local timezone from the DataContext.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)