-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hi,

MySQL Connector/J 3.1.2, a new version of the Type-IV all-Java JDBC driver for MySQL has been released.

Version 3.1.2 is a new feature release for the ALPHA tree that is suitable for use with either MySQL-4.1 or MySQL-5.0 (and is required when using server-side prepared statements on MySQL-4.1.2 or newer).

It is now available in source and binary form from the Connector/J download pages at http://www.mysql.com/downloads/api-jdbc-stable.html and mirror sites (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.)

Please note that currently server-side prepared statements are automatically disabled in this release when the driver is connecting to MySQL-5.0.0 or MySQL-5.0.1, as the current prepared statement code from the 4.1 branch (which contains network protocol-level changes) has yet to be merged into the 5.0 source tree.

Depending on bug reports from the field, and how the release time line for MySQL-4.1 plays out, this release should be the last ALPHA release of the Connector/J 3.1 series.

The focus of the next release of Connector/J 3.1 is on code cleanup and performance improvements (although micro-performance benchmarks are looking pretty good right now, approx 25-30% faster than the 3.0 series due mostly to shortening call stack length and some optimizations in re-using expensive to allocate objects).

Have fun with this release!

Please take the time to file any bugs you might encounter (hopefully none!) at http://bugs.mysql.com/ ... We're particularly interested in any issues you might have with this release and MySQL-4.1.2 with respect to server-side prepared statements.

Regards,

-Mark

- From the changelog:

06-09-04 - Version 3.1.2-alpha

- Fixed stored procedure parameter parsing info when size was specified for a parameter (i.e. char(), varchar()).

- Enabled callable statement caching via 'cacheCallableStmts' property.

- Fixed case when no output parameters specified for a stored procedure caused a bogus query to be issued to retrieve out parameters, leading to a syntax error from the server.

- Fixed case when no parameters could cause a NullPointerException in CallableStatement.setOutputParameters().

- Removed wrapping of exceptions in MysqlIO.changeUser().

- Fixed sending of split packets for large queries, enabled nio ability to send large packets as well.

- Added .toString() functionality to ServerPreparedStatement, which should help if you're trying to debug a query that is a prepared statement (it shows SQL as the server would process).

- Added 'gatherPerformanceMetrics' property, along with properties to control when/where this info gets logged (see docs for more info).

- ServerPreparedStatements weren't actually de-allocating server-side resources when .close() was called.

- Added 'logSlowQueries' property, along with property 'slowQueriesThresholdMillis' to control when a query should be considered 'slow'.

- Correctly map output parameters to position given in prepareCall() vs. order implied during registerOutParameter() - fixes BUG#3146.

- Correctly detect initial character set for servers >= 4.1.0

- Cleaned up detection of server properties.

- Support placeholder for parameter metadata for server >= 4.1.2

- Fix for BUG#3539 getProcedures() does not return any procedures in result set

- Fix for BUG#3540 getProcedureColumns() doesn't work with wildcards for procedure name

- Fixed BUG#3520 -- DBMD.getSQLStateType() returns incorrect value.

- Added 'connectionCollation' property to cause driver to issue 'set collation_connection=...' query on connection init if default collation for given charset is not appropriate.

- Fixed DatabaseMetaData.getProcedures() when run on MySQL-5.0.0 (output of 'show procedure status' changed between 5.0.1 and 5.0.0.

- Fixed BUG#3804 -- getWarnings() returns SQLWarning instead of DataTruncation

- Don't enable server-side prepared statements for server version 5.0.0 or 5.0.1, as they aren't compatible with the '4.1.2+' style that the driver uses (the driver expects information to come back that isn't there, so it hangs). -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAxj0wtvXNTca6JD8RAvfQAJ46YtLfHBBIg6MUtjBmwWpwT1rMnQCcDMpi DKOuvoQ3088UuwRUKN90rlE= =s1tz -----END PGP SIGNATURE-----