Quantcast
Channel: MySQL Forums - Announcements
Viewing all articles
Browse latest Browse all 1041

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

$
0
0
Dear MySQL Users,

MySQL Connector/J 5.1.28, 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.28 is suitable for use with many MySQL server versions,
including 4.1, 5.0, 5.1, 5.4 and 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.

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.28 includes the following general bug fixes
and improvements, also listed in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-28.html

Changes in MySQL Connector/J 5.1.28 (2013-12-23)

   Functionality Added or Changed

     * Added support for live management for replication hosts. This
       enables users to change replication topographies (for example,
       adding or removing a host, or promoting a salve to master)
       without having to restart an application. See Section, 8.3,
       "Master/Slave Replication with ReplicationConnection," for
       details. (Bug #70842)

   Bugs Fixed

     * A shadow declaration of
       com.mysql.jdbc.OperationNotSupportedException is removed from
       com.mysql.jdbc.RowDataDynamic. (Bug #17833137, Bug #70969)

     * An incorrect SQLException subclass was thrown during a query
       interruption. This fix creates a new, JDBC4-specific version
       of MySQLQueryInterruptedException, which subclasses
       MySQLNonTransientException. (Bug #17750877, Bug #70835)

     * When the connection property dontTrackOpenResources=true was
       used, the result set was closed after a Statement.close() was
       issued. (Bug #17164058, Bug #69746)

     * A validation is added to check if blobSendChunkSize is
       negative (which is the case when maxAllowedPacket is set with
       a value less than or equal to "8203") when
       useServerPrepStmts=true. It throws an exception when the
       validation fails. (Bug #17184082, Bug #69777)

     * The timeout limit set by DriverManager.setLoginTimeout() was
       not honored during a handshake attempt. This fix adds the
       DriverManager.setLoginTimeout() control to the function
       NonRegisteringDriver.connect(): if the defined timeout is
       reached, the connection creation is cancelled and an exception
       is thrown. (Bug #17015317, Bug #69579)

     * The method Statement.closeOnCompletion() was not working. (Bug
       #16691047, Bug #68916)

     * Connector/J's SQL escape sequence processor was confused by
       multiple backslashes. The EscapeTokenizer has been re-factored
       to process multiple backslashes properly. (Bug #11759035, Bug
       #51313)

     * With cacheResultSetMetadata=true, cacheCallableStmts=true, and
       cachePrepStmts=true, if a stored procedure that returns a
       result set was called, calling the stored procedure a second
       time resulted in a null pointer exception being thrown for
       initializeResultsMetadataFromCache. (Bug #11762713, Bug
       #55340)

Thanks,

On behalf of Oracle/MySQL Build Team,
Murthy Narkedimilli

Viewing all articles
Browse latest Browse all 1041

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>