You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/11/14 09:09:10 UTC
[jira] [Resolved] (CALCITE-964) Rename "timezone" connection
property to "timeZone"
[ https://issues.apache.org/jira/browse/CALCITE-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Julian Hyde resolved CALCITE-964.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.6.0
Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/bb333e20.
> Rename "timezone" connection property to "timeZone"
> ---------------------------------------------------
>
> Key: CALCITE-964
> URL: https://issues.apache.org/jira/browse/CALCITE-964
> Project: Calcite
> Issue Type: Bug
> Reporter: Julian Hyde
> Assignee: Julian Hyde
> Fix For: 1.6.0
>
>
> Rename "timezone" connection property to "timeZone", to be consistent with java.util.TimeZone (two words in camel case). Also rename CalciteConnectionProperty.TIMEZONE and BuiltInConnectionProperty.TIMEZONE to TIME_ZONE.
> ConnectionConfig.timeZone() is already OK.
> Connect string properties are matched case-insensitively, and so "jdbc:calcite:timezone=gmt+3" will continue to work. So will "timeZone", "TIME_ZONE", "TIMEZONE".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)