MySQL Connector/J 5.1.20

MySQL Connector/J is a JDBC Type 4 driver and allows connecting Java-based apps to MySQL databases.

MySQL Connector/J is perfect for small to medium scaled apps. For large scale apps, it is recommended using advanced Java persistence frameworks like Spring or Hibernate.

MySQL Connector/C++ is licensed under the GPL with a commercial license upon request.

What's New in This Release: [ read full changelog ]

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 to CharsetMapping.java

Bugs Fixed:
· The LRUCache implementation removed the eldest entry, rather than the least-recently accessed. (Bug #13036537)
· Changed cacheCallableStatements to cacheCallableStmts in maxPerformance.properties, to allow proper caching. (Bug #13036309)
· Added a new ant flag, com.mysql.jdbc.junit.fork, which controls whether JUnit will fork new processes.
· The value on: The default, and legacy behavior. Or off): Required for Windows, as otherwise process fork failure errors will result while running the test suite via ant on Windows. (Bug #12784170)
· Not putting a space between VALUES() and ON DUPLICATE KEY UPDATE causes connector/J to both (A) Rewrite the query, although it includes an ON UPDATE statment and (B) To generate the wrong query with multiple ON DUPLICATE KEY statements. (Bug #12565726)
· The "old" warnings were returned when Statement.getWarnings() was called after Statement.clearWarnings(). (Bug #61866, Bug #12791594)
· Calling 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 KILL QUERY (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 possible. (Bug #61501)
· A connection could not be established when the URL contained both sessionVariables and characterEncoding. (Bug #61201, Bug #12649557)
· Reverting changes made to ConnectionImpl.java, the private boolean characterSetNamesMatches function.