Bug #73012 precedence between timezone options is unclear

• Submitted: 15 Jun 2014 20:04
• Modified: 9 Jan 2015 9:44
• Reporter: Paul Baclace
• Status: Closed
• Category: Connector / J Documentation
• Severity: S3 (Non-critical)
• Version: 5.1
• OS: Any
• Assigned to: Filipe Silva
• CPU Architecture: Any

[15 Jun 2014 20:04] Paul Baclace

Description:
The documentation should be less puzzling on the precedence relationship between:

  useTimezone
  useLegacyDatetimeCode
  useJDBCCompliantTimezoneShift

Notice useJDBCCompliantTimezoneShift says"exclusive of useTimezone=true", but stating which setting takes precedence over the other would be more clear. The phrase "exclusive of" can mean "not considering" or exclusive-or. 

 

How to repeat:
view connector/j 5.1 documentation and read the text.

[15 Jul 2014 17:16] Sveta Smirnova

Thank you for the report.

Verified as described. Indeed documentation for useJDBCCompliantTimezoneShift  at http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.htm... can be less confusing.

[14 Oct 2014 21:38] Daniel So

Descriptions for the properties useTimezone, useLegacyDatetimeCode,and useJDBCCompliantTimezoneShift have been updated. Their inter-relationships are now clearly explained. Please see http://dev.mysql.com/doc/connector-j/en/connector-j-reference-configuration-properties.htm....