MySQL version since 4.1 (It will not work with 4.0 or earlier releases.)

Functionality added or changed:

* Options in the GUI are grouped on named tabs.

* Added connection option INTERACTIVE that tells driver that client is interactive and interactive_timeout has to be used. (Bug #48603)

* Added parameters arrays support. (Bug #48310)

* SQLTables uses now INFORMATION_SCHEMA. Added connection option to use old code. (Bug #43644)

* Added GUI options for MIN_DATE_TO_ZERO and ZERO_DATE_TO_MIN connection options. (Bug #30539)

Bugs fixed:

* If NO_BACKSLASH_ESCAPES mode is used on a server, escaping binary data can lead to server query parsing errors. (Bug #49029)

* Error if unsupported client character set is encountered(for wchar data). (Bug #36996)

* Binding bit field to a numeric types doesn’t work. (Bug #32821)

* Conversion flags are not complete. (Bug #43855)

* SQL_ATTR_MAX_ROWS make some SELECT statement invalid. (Bug #49726)

* Certain column attributes aren’t correct for date columns. (Bug 44576)

* SQLPrepare causes Prefetch of table. (Bug #46411)

* If there are foreign key constraints with same name for tables with same names in 2 schemas, SQLForeignKeys can return rows for both schemas in query about one of those tables. (Bug #49660)

* SQLForeignKeys included in results rows for foreign keys pointing to unique fields (Bug #51422)

* SQLPrimaryKeys returns mangled strings. (Bug #36441)

* Spaces in connection string aren’t removed (Bug #45378)

* SQLColumns returns wrong transfer octet length. (Bug #53235)

* Retrieving of current catalog at the moment when connection is not ready for that(broken, not all pending results processed) leads to application crash. (Bug #46910)

* SQLForeignKeys unacceptable performance getting imported FK. (Bug #39562)

* SQLTablePrivileges requires SELECT privilege on mysql database. (Bug #50195)

* Column octet length includes terminating null byte. (Bug #54206)

* Wrong type returned by SQLColAttribute(SQL_DESC_PRECISION…) in 64-bit systems. (Bug #55024)

Built against the client library from MySQL  5.1.46sp1

Version 5.1.13 is suitable for use with any MySQL version including MySQL-5.0, MySQL-5.1 or MySQL-5.5.

It is now available in source and binary form from the Connector/J download pages at:  http://dev.mysql.com/downloads/connector/j/5.1.html

As always, we recommend that you check the change log  http://dev.mysql.com/doc/refman/5.1/en/cj-news.html and “Upgrading” sections  http://dev.mysql.com/doc/refman/5.1/en/cj-upgrading.html in the manual before upgrading as well as the “CHANGES” file in the download archive to be aware of changes in behavior that might affect your application.

MySQL Connector/J 5.1.13 includes the following changes targeted at scalability and performance:

- Fixed Bug#51266 – jdbc:mysql:loadbalance:// would stick to the first host in the list in some cases, especially exacerbated if the host was down.

- Replaced URLs of the form jdbc:mysql://host-1,host-2 with a composite of a normal connection and a jdbc:mysql:loadbalance:// connection for more robustness and cleaner code.

- Fixed BUG#51643 – Connections using jdbc:mysql:loadbalance:// would have statements (and prepared statements) that did not have their connections changed upon commit()/rollback(), and thus applications that held statement instances past commit()/rollback() could have data written to or read from un-intended connections.

- Fixed BUG#51783 – Load-balanced connections could throw a SQLException incorrectly on commit() or rollback().  This was not caused by failures in commit or rollback, but rather by the possibility that the newly-selected physical connection was stale.  Added logic to catch and retry if this happens, up to the number of hosts specified for load-balancing.  Also added new property,      loadBalanceValidateConnectionOnSwapServer, which controls whether to explicitly ping the selected host (otherwise, the host is presumed to be up, and will only be noticed if auto-commit or transaction isolation state needs to be set and fails).

- Added loadBalancePingTimeout property to allow a specific timeout to be set for each ping executed against the servers.  This ping is executed when the physical connections are rebalanced (commit/rollback or communication exception), or when a query starting with (exactly) “/* ping */” is executed.  The latter causes each open underlying physical connection to be pinged.

- Fixed BUG#51776 – Connection.rollback() could swallow exceptions incorrectly.

- Fixed BUG#52231 – Differences in definitions of which SQLExceptions trigger a failover event could result in failure to try more than a single host in certain situations.

- Fixed BUG#52534 – Performance regression using load-balanced connection.

- More aggressively purge the statement timeout timers after they’ve been cancelled to trade time for memory. This purge only happens if statement timeouts are in use.

- Added management of running load-balanced connections.  Statistics can be obtained, and hosts added/dropped via com.mysql.jdbc.ConnectionGroupManager or the JMX implementation.  This functionality is enabled by setting the new parameter “loadBalanceConnectionGroup” to the name of the logical grouping of connections.

All load-balanced connections sharing the same loadBalanceConnectionGroup value, regardless of how the application creates them, will be managed together.  To enable JMX-based management, set loadBalanceEnableJMX=true and ensure that remote      JMX is enabled in the JRE (eg, use -Dcom.sun.management.jmxremote).

- Added loadBalanceExceptionChecker property, which takes a fully-qualified class name implementing the com.mysql.jdbc.LoadBalancedExceptionChecker interface.  This allows custom evaluation of SQLExceptions thrown to determine whether they should trigger failover to an alternate host in load-balanced deployments.  The default is com.mysql.jdbc.StandardLoadBalanceExceptionChecker.

- Added two new properties which allow more flexibility in determining which SQLExceptions should trigger failover in a load-balanced deployment.  The new “loadBalanceSQLStateFailover” property takes a comma-delimited list of SQLState codes which are compared to the SQLState of the SQLException (matching done with trailing wildcard), while “loadBalanceSQLExceptionSubclassFailover” takes a comma-delimited list of fully-qualified class/interface names, against which the SQLException is checked to determine if it is an instance of any. Matches trigger failover to an alternate host.

- Fixed Bug#51704 – Re-written batched statements don’t honor escape processing flag of their creator.

As well as the following general bug fixes and improvements:

- Fixed BUG#51666 – StatementInterceptors were never “un-safed” after connection establishment, causing interceptors which returned result sets pre/post execution would not work.

- Minor fix in previous patch for Bug#51904. Function ConnectionImpl.setCatalog() was passed quoted argument thus breaking with “…for the right syntax to use near ‘test“’”

- Fix for Bug#51912 – Passing NULL as cat. param to getProcedureColumns with !nullCatalogMeansCurrent

- Fix for Bug#52167 – Can’t parse parameter list with special characters inside

- Fix for Bug#51904 – getProcedureColumns() always returns PROCEDURE_CAT result column as NULL

- Fix for Bug#51712 – Display Size is always 0 for columns returned by getProcedureColumns()

- Fix for Bug#51908 – db variable might have end up unassigned when calling getProcedureColumns()/Functions(). This is a followup on code changes made for Bug#51022.

- Fixed Bug#43576 – Sometimes not able to register OUT parameters for  CallableStatements.

- Fixed Bug#54175 – Driver doesn’t support utf8mb4 for servers 5.5.2 and newer. The driver now auto-detects servers configured with character_set_server=utf8mb4 or treats the Java encoding “utf-8″ passed via “characterEncoding=…” as utf8mb4 in the “SET NAMES=” calls it makes when establishing the connection.

Version 5.1.11 is suitable for use with any MySQL version including MySQL-5.0, MySQL-5.1 or MySQL-5.5.

It is now available in source and binary form from the Connector/J download pages at

http://dev.mysql.com/downloads/connector/j/5.1.html

and mirror sites as well as Maven-2 repositories (note that not all mirror sites may be up to date at this point of time – if you can’t find this version on some mirror, please try again later or choose another download site.)

As always, we recommend that you check the change log

http://dev.mysql.com/doc/refman/5.1/en/cj-news.html

and “Upgrading” sections

http://dev.mysql.com/doc/refman/5.1/en/cj-upgrading.html

in the manual before upgrading as well as the “CHANGES” file in the download archive to be aware of changes in behavior that might affect
your application.

We welcome and appreciate your feedback, bug reports, bug fixes, patches etc.:

http://forge.mysql.com/wiki/Contributing

MySQL Connector/J 5.1.11 includes the following changes targeted at scalability and performance:

- Fix for BUG#50288 – NullPointerException possible during invalidateCurrentConnection() for load-balanced connections.

- Fix for BUG#48605 – Ping for load balanced connections leaves closed connections in liveConnections, causing subsequent Exceptions when that connection is used.

- Fix for BUG#48442 – Load-balanced Connection object returns inconsistent results for hashCode() and equals() dependent upon state of underlying connections.

- Fix for BUG#48172 – Batch rewrite requires space immediately after “VALUES”

- Fix for BUG#48486 Cannot use load balanced connections with MysqlConnectionPoolDataSource.

- “Replication” connections (those with URLs that start with
jdbc:mysql:replication) now use a jdbc:mysql:loadbalance connection
under the hood for the slave “pool”. This also means that one can set
load balancing properties such as “loadBalanceBlacklistTimeout” and
“loadBalanceStrategy” to choose a mechanism for balancing the load and
failover/fault tolerance strategy for the slave pool. This work was done
in order to fix Bug#49537.

- Fixed Bug#36565 – permgen leak from java.util.Timer. Unfortunately no great
fix exists that lets us keep the timer shared amongst connection instances, so
instead it’s lazily created if need be per-instance, and torn down when the
connection is closed.

- Fixed BUG#49700 – Connections from ConnectionPoolDataSource don’t
maintain any values set with “sesssionVariables=…”. This was a bug
in Connection.changeUser()/resetServerState(), we now resubmit the
session variables during the execution of these methods.

(special thanks to Todd Farmer from the Sun/MySQL support team for the numerous fixes to load-balanced connections!)

As well as the following general bug fixes and improvements:

- Fix for BUG#49607 – Provide Connection context in ExceptionInterceptor.

- Fix for BUG#49745 – deleteRow() for updatable result sets can cause full table scan because escaped hex values are used for primary key identifiers.

- Fix for Bug#32525 – “noDatetimeStringSync” doesn’t work for server-side prepared statements. Now it does.

- Hooked up exception interceptors so they get called now.

- Rev’d the statement interceptor interface to pass on some server flags, warning counts and errors. See
the com.mysql.jdbc.StatementInteceptorsV2 interface for more details. The driver will create adaptors to
transparently convert older implementations to the newer interface at runtime.

- Statement Interceptors are now enabled at connection instantiation, but
can not return result sets (they will be ignored) until the connection
has bootstrapped itself. If during the init() method your interceptor
requires access to the connection itself, it should ensure that methods
that might throw exceptions if the connection is closed should handle
this in a robust manner.

- Statement Interceptors didn’t completely intercept server-side prepared statements.