MySQL Connector/J 5.1 Developer Guide
The following are some known issues and limitations for MySQL Connector/J 5.1:
When Connector/J retrieves timestamps for a daylight saving
time (DST) switch day using the
getTimeStamp()
method on the result set,
some of the returned values might be wrong. The errors can be
avoided by using the following connection options when
connecting to a database:
useTimezone=true useLegacyDatetimeCode=false serverTimezone=UTC
Since release 5.1.41, the functionality of the property
elideSetAutoCommits
has been disabled due
to Bug# 66884. Any value given for the property is ignored by
Connector/J.
MySQL Server uses a proleptic Gregorian calendar internally.
However, Connector/J uses java.sql.Date
,
which is non-proleptic. Therefore, when setting and retrieving
dates that were before the Julian-Gregorian cutover (October
15, 1582) using the PreparedStatement
methods, always supply explicitly a proleptic Gregorian
calendar to the setDate()
and
getDate()
methods, in order to avoid
possible errors with dates stored to and calculated by the
server.
For MySQL 8.0.14 and later, 5.7.25 and later, and
5.6.43 and later: To use Windows named pipes for
connections, the MySQL Server that Connector/J wants to
connect to must be started with the system variable
named_pipe_full_access_group
;
see Section 5.9, “Connecting Using Named Pipes” for details.