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

Hi,

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

Version 3.2.0 is the first ALPHA release of the 3.2 series that is
suitable for use with all versions of MySQL, including MySQL-4.1 or
MySQL-5.0. Connector/J 3.2.0 is required if you want to use the new
batched fetching capability of MySQL-5.0 when using prepared statements.

It is now available in source and binary form from the Connector/J
download pages at http://dev.mysql.com/downloads/connector/j/3.2.html
as well as 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.)

If you are upgrading from Connector/J 3.0, or are upgrading from
MySQL-4.0 to MySQL-4.1, please make sure to check out the 'Upgrades'
section in the documentation that comes with the driver, or available on
the web site at http://dev.mysql.com/doc/connector/j/en/#id2424819

Connector/J 3.1 is the current production series of drivers, as was
announced earlier.

        -Mark

- From the changelog:

12-23-04 - Version 3.2.0-alpha

- - Fixed incorrect return values from
DatabaseMetaData.supportsCatalogIn*().

- - Support for 'cursor' based result sets when using
ServerPreparedStatements and MySQL 5.0 or newer. Result set needs to be
forward-only, and a non-zero fetch size for this feature to be enabled.

- - Refactoring of where logic for prepared statement, server-prepared
statement lives.

- --
Mark Matthews
MySQL AB, Software Development Manager - Client Connectivity
www.mysql.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFB5B3EtvXNTca6JD8RArYAAJ9N4p4CQ1fHVW7Mh+aJ6BtzjURT6QCfTfqw
BH3m+IgmH66PWJbb1EIAWwc=
=/kSb
-----END PGP SIGNATURE-----

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to