MySQL Connector/J 5.1.27 has been released (no replies)

Hello all,

MySQL Connector/J 5.1.27, a maintenance release of the production
5.1 branch has been released. Connector/J is the Type-IV pure-Java
JDBC driver for MySQL.

Version 5.1.27 is suitable for use with many MySQL server versions,
including 4.1, 5.0, 5.1, 5.4, 5.5 and 5.6.

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.

As always, we recommend that you check the "CHANGES" file in the
download archive to be aware of changes in behavior that might affect
your application.

MySQL Connector/J 5.1.27 includes the following general bug fixes and
improvements, also available in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-27.html

Changes in MySQL Connector/J 5.1.27 (2013-11-04)

   Functionality Added or Changed

     * Added support for EXPLAIN for UPDATE and DELETE. Extended
       slow query warning with query execution plan for INSERT,
       REPLACE, UPDATE, and DELETE.

     * Added the flag CLIENT_PLUGIN_AUTH_LENENC_CLIENT_DATA and
       support for authentication data up to a length of (2^64)-1
       bytes.

   Bugs Fixed

     * When attempting to connect to a server using long,
       multi-byte user name and database name, an Array Index
       Out Of Bounds Exception was thrown. This fix prevents the
       problem by increasing the space reserved for those
       strings. (Bug #17251955)

     * When setting a connection property with a value for
       blobSendChuckSize, largeRowSizeThreshold, or
       locatorFetchBufferSize, the suffix "G" was not recognized
       and caused an error to be thrown. With this fix,
       Connector/J now supports using "G" or "GB" for gigabyte
       for the purpose, as well as "KB" for kilobyte and "MB"
       for megabyte. (Bug #17015673, Bug #69452)

     * When there was an attempt to create a second branch with
       a duplicate ID on the same MySQL server instance, the
       XAException.errorCode returned by Connector/J was not
       equal to XAException.XAER_DUPID. (Bug #16979862, Bug
       #69506)

     * The SYSTEM TABLE type was handled inconsistently in
       different methods: DatabaseMetaData.getTableTypes() did
       not return system tables, and
       DatabaseMetaData.getTables() did not return all system
       tables. With this fix, the table types SYSTEM TABLE and
       SYSTEM VIEW are returned by getTableTypes(), and
       getTables() now returns tables from the internal schemas
       mysql and performance_schema as instances of SYSTEM TABLE
       and tables from information_schema as instances of SYSTEM
       VIEW. (Bug #16879239, Bug #69290)

     * JDBC authentication failed when there was a null byte in
       the scramble, because com.mysql.jdbc.MysqlIO.doHandshake
       only read up to the first null byte when reading in the
       first eight bytes of the scramble. (Bug #16723048, Bug
       #62469)

     * When rewriteBatchedStatements=true and
       useAffectedRows=true were set, executeBatch() did not
       return the number of affected rows as expected. (Bug
       #16442951, Bug #68562)

     * Calling ResultSet.absolute(0) caused Connector/J to throw
       an error. This fix makes ResultSet.absolute(0) behave
       like ResultSet.beforeFirst(), as required by the JDBC
       specifications. (Bug #11749136, Bug #38252)

     * The string returned by
       DatabaseMetaData.getDriverVersion() contains the
       unexpanded expression "${svn.Revision}" or
       "${bzr.revision-id}" instead of the actual revision
       number of Connector/J. (Bug #50538, Bug #11758345)


Thanks,

MySQL/ORACLE Build Team