[
https://issues.apache.org/jira/browse/CALCITE-964?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Julian Hyde updated CALCITE-964:
--------------------------------
Description:
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".
was:
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:timezoze=gmt+3" will continue to work. So will "timeZone",
"TIME_ZONE", "TIMEZONE".
> 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
>
> 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)
