From: Hery Ramilison
Date: September 11 2012 12:09am
Subject: MySQL Connector/J 5.1.22 has been released
List-Archive: http://lists.mysql.com/java/9357
Message-Id: <504E8132.7050204@oracle.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hello all,

MySQL Connector/J 5.1.22, 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.21 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.

We welcome and appreciate your feedback, bug reports, bug fixes, patches
etc: http://forge.mysql.com/wiki/Contributing

- Fix for Bug#57662, With profileSQL=true and
     useNanosForElapsedTime=true specified in the connection URL, query
     and fetch duration were not reported correctly.

   - Fix for Bug#65503, ResultSet objects created by the
     getGeneratedKeys() method were not being automatically closed,
     leading to potential memory leaks if the application did not
     explicitly close the ResultSet objects.

   - Fix for Bug#63800, getVersionColumns() does not return timestamp
     fields; always empty.  Added support of ON UPDATE
     CURRENT_TIMESTAMP for TIMESTAMP and DATETIME fields.

   - Fix for Bug#41752, Connecting to a server that used a UCS2
     character set would throw an exception

   - Fix for Bug#65508, The com.mysql.jdbc.getCharsetNameForIndex()
     method was made more efficient, resulting in better performance
     for queries against tables containing many columns with string
     data types.

   - Fix for Bug#14563127, The
     LoadBalancingConnectionProxy.pickNewConnection() method could
     incorrectly flag the current connection as invalid after testing
     another connection.

Enjoy!