Fixes bugs found since release 5.1.17.
Functionality Added or Changed
Added the function
MYSQL_INDEX_TO_MYSQL_CHARSET to retrieve the
server charset name, using an index instead of parsing variables
LRUCache implementation removed the
eldest entry, rather than the least-recently accessed.
maxPerformance.properties, to allow proper
Added a new
com.mysql.jdbc.junit.fork, which controls
JUnit will fork new processes for
testing. Valid values for the flag are:
on: fork new process; the default and
off: do not fork new process; required
for Windows, or
process fork failure
errors will result while running the test suite via
ant on Windows.
Not putting a space between
DUPLICATE KEY UPDATE causes connector/J to both (A)
Rewrite the query, although it includes an
UPDATE statement and (B) To generate the wrong query
DUPLICATE KEY statements.
loadBalanceBlacklistTimeout option was
not functioning properly. Working connections were not being
removed from the blacklist.
Connector/J now guards against the condition where a call to
KILL QUERY will
kill the next query issued by the server, if no query is in
The "old" warnings were returned when
Statement.getWarnings() was called after
(Bug #61866, Bug #12791594)
Statement.cancel() on a statement
that isn't currently executing, will cause a later-executed
query on the same connection to be unexpectedly canceled. The
driver now guards against this condition, but it is an
underlying server issue. The MySQL statement
(which is what the driver uses to implement
Statement.cancel()) is rather
non-deterministic, and thus the use of
Statement.cancel() should be avoided if
A connection could not be established when the
URL contained both
(Bug #61201, Bug #12649557)
Reverting changes made to
boolean characterSetNamesMatches function.