MySQL Connector/J 5.1.15 Has Been Released

Mark Matthews <[email protected]> Thu, 10 Feb 2011 08:55:14 -0600
Newsgroups gmane.comp.db.mysql.java
Message-ID <[email protected]>
Hi,

MySQL Connector/J 5.1.15, 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.15 is suitable for use with any MySQL version including =
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 or repositories 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.15 includes the following general bug fixes and =
improvements:

   - Fix for Bug#38367, parameters metadata did not reflect the fact =
that NULL is allowed
     parameter value. So DatabaseMetaData.getProcedureColumns will set =
isNullable member to
     java.sql.DatabaseMetaData.procedureNullable now.

   - Fix for Bug#27916, DatabaseMetaData.getTypeInfo() does not return =
all the available=20
      data types.

   - Fix for Bug#59224, adding 5.5 reserved words to =
DatabaseMetaData.getSQLKeywords().

   - Fixed an issue where statement comments set via =
Connection.setStatementComment()
     weren't represented in autoGenerateTestcaseScript=3Dtrue output.

   - Added ability to include the current java thread dump in the =
exception message
     given for deadlock/wait lock timeout exceptions, enable with
     "includeThreadDumpInDeadlockExceptions=3Dtrue" in your JDBC url.

   - Added ability to include current thread name as a statement comment =
visible
     in MySQL's "SHOW PROCESSLIST" and Innodb deadlock diagnostics, =
enable with
     "includeThreadNamesAsStatementComment=3Dtrue".

   - Added an SLF4J logging adapter. Enable by adding setting the =
connection
     property "logger" to "Slf4JLogger" and placing the appropriate =
bridge
     from SLF4J to the logging framework of choice in your CLASSPATH. As =
with
     other Connector/J logging adapters, the log category name used by =
the
     driver is "MySQL". See http://www.slf4j.org/manual.html for more =
details.

Enjoy!

	-Mark
--=20
Mark Matthews
Principal Software Developer -  MySQL Enterprise Tools
Oracle
http://www.mysql.com/products/enterprise/monitor.html








-- 
MySQL Java Mailing List
For list archives: http://lists.mysql.com/java
To unsubscribe:    http://lists.mysql.com/[email protected]