10bet网址
MySQL Connector/J 5.1 Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr)- 0.6Mb
PDF (A4)- 0.6Mb


MySQL Connector/J 5.1 Release Notes/在MySQL连接器/变化J 5.1/ Changes in MySQL Connector/J 5.1.43 (2017-07-21)

在MySQL连接器/变化J 5.1.43 (2017-07-21)

Version 5.1.43 is a maintenance release of the production 5.1 branch. It is suitable for use with MySQL Server versions 5.5, 5.6, and 5.7. It supports the Java Database Connectivity (JDBC) 4.2 API.

Functionality Added or Changed

  • Connecting to MySQL Server 8.0.3 using Connector/J resulted in anSQLException: Unknown system variable 'query_cache_size', because the query cache has been removed from the server. All query cache server variables and functionality has now been removed from Connector/J 5.1. (Bug #26399958)

  • Updated the timezone mappings using the latest IANA and CLDR time zone databases. (Bug #25946965)

  • A new option for theloadBalancingStrategyconnection property calledserverAffinityhas been added. The servers listed in the new connection propertyserverAffinityOrder(which should be a subset of the servers in the host list of the connection URL) are contacted in the order they are listed until a server is available or until the list of servers is exhausted, at which point a random load-balancing strategy is used with the hosts not listed byserverAffinityOrder. See descriptions forloadBalancingStrategyandserverAffinityOrderinConfiguration Properties for Connector/Jfor details. (Bug #20182108)

Bugs Fixed

  • Secure JDBC connections did not fall back to the default truststore when a custom one was not provided. (Bug #26243128)

  • Connector/J failed a number of regression tests in the testsuite related to geographic information system (GIS) functions because of changes to GIS support by the MySQL server. The fix corrects the tests. (Bug #26239946, Bug #26140577)

  • Attempts to connect to a server started with collationutf8mb4_de_pb_0900_ai_ciresulted in null pointer exceptions. (Bug #26090721)

  • Incom/mysql/jdbc/ServerPreparedStatement.java, the argumentsresultSetTypeandresultSetConcurrencyfor a call ofConnection.preparedStatement()were swapped. (Bug #25874048, Bug #85885)

  • ANullPointerExceptionwas returned whengetDate(),getTime(), orgetTimestamp()was called with a nullCalendar. This fix makes Connector/J throw anSQLExceptionin the case. (Bug #25650305)

  • Some JDBC proxied objects were missing the proper handlings of theequals()methods, thus even comparison of one of these proxied objects to its own self withequals()yielded false. This patch introduces proper handlings for theequals()method in all the relevant proxies. (Bug #21931572, Bug #78313)

  • A server-side prepared statement was not closed when the same statement was being prepared again while the original statement was being cached. This was caused by the silent replacement of the cache entry of the old statement by the new. When this happened repeatedly, it caused eventually the complaint thatmax_prepared_stmt_countwas exceeded. This fix makes sure that when a cache entry for a statement replaces an older one, the older statement is immediately closed. (Bug #20066806, Bug #74932)