-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
MySQL Connector/J 3.1.7, a new version of the Type-IV all-Java JDBC
driver for MySQL has been released.
Version 3.1.7 is the latest production release of the 3.1 series that is
suitable for use with all versions of MySQL, including MySQL-4.1 or
MySQL-5.0. Connector/J 3.1.7 is required if you want to use server-side
prepared statements with MySQL-4.1.2 or newer, or CallableStatements
with MySQL-5.0.
Sources and binaries are now available from the Connector/J
download pages at http://dev.mysql.com/downloads/connector/j/3.1.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/cj-upgrading-3-0-to-3-1.html
-Mark
- From the changelog:
02-18-05 - Version 3.1.7-stable
- Fixed BUG#7686, Timestamp key column data needed "_binary'"
stripped for UpdatableResultSet.refreshRow().
- Fixed BUG#7715 - Timestamps converted incorrectly to strings
with Server-side prepared statements and updatable result sets.
- Detect new sql_mode variable in string form (it used to be
integer) and adjust quoting method for strings appropriately.
- Added 'holdResultsOpenOverStatementClose' property (default is
false), that keeps result sets open over statement.close() or new
execution on same statement (suggested by Kevin Burton).
- Fixed BUG#7952 -- Infinite recursion when 'falling back' to master
in failover configuration.
- Disable multi-statements (if enabled) for MySQL-4.1 versions prior
to version 4.1.10 if the query cache is enabled, as the server
returns wrong results in this configuration.
- Fixed duplicated code in configureClientCharset() that prevented
useOldUTF8Behavior=true from working properly.
- Removed 'dontUnpackBinaryResults' functionality, the driver now
always stores results from server-side prepared statements as-is
from the server and unpacks them on demand.
- Fixed BUG#8096 where emulated locators corrupt binary data
when using server-side prepared statements.
- Fixed synchronization issue with
ServerPreparedStatement.serverPrepare() that could cause
deadlocks/crashes if connection was shared between threads.
- By default, the driver now scans SQL you are preparing via all
variants of Connection.prepareStatement() to determine if it is a
supported type of statement to prepare on the server side, and if
it is not supported by the server, it instead prepares it as a
client-side emulated prepared statement (BUG#4718). You can
disable this by passing 'emulateUnsupportedPstmts=false' in your
JDBC URL.
- Remove _binary introducer from parameters used as in/out
parameters in CallableStatement.
- Always return byte[]s for output parameters registered as *BINARY.
- Send correct value for 'boolean' "true" to server for
PreparedStatement.setObject(n, "true", Types.BIT).
- Fixed bug with Connection not caching statements from
prepareStatement() when the statement wasn't a server-side
prepared statement.
- Choose correct 'direction' to apply time adjustments when both
client and server are in GMT timezone when using
ResultSet.get(..., cal) and PreparedStatement.set(...., cal).
- Added 'dontTrackOpenResources' option (default is false, to be
JDBC compliant), which helps with memory use for non-well-behaved
apps (i.e applications which don't close Statements when they
should).
- Fixed BUG#8428 - ResultSet.getString() doesn't maintain format
stored on server, bug fix only enabled when 'noDatetimeStringSync'
property is set to 'true' (the default is 'false').
- Fixed NPE in ResultSet.realClose() when using usage advisor and
result set was already closed.
- Fixed BUG#8487 - PreparedStatements not creating streaming result
sets.
- Don't pass NULL to String.valueOf() in
ResultSet.getNativeConvertToString(), as it stringifies it (i.e.
returns "null"), which is not correct for the method in question.
- Fixed BUG#8484 - ResultSet.getBigDecimal() throws exception
when rounding would need to occur to set scale. The driver now
chooses a rounding mode of 'half up' if non-rounding
BigDecimal.setScale() fails.
- Added 'useLocalSessionState' configuration property, when set to
'true' the JDBC driver trusts that the application is well-behaved
and only sets autocommit and transaction isolation levels using
the methods provided on java.sql.Connection, and therefore can
manipulate these values in many cases without incurring
round-trips to the database server.
- Added enableStreamingResults() to Statement for connection pool
implementations that check Statement.setFetchSize() for
specification-compliant values. Call Statement.setFetchSize(>=0)
to disable the streaming results for that statement.
- Added support for BIT type in MySQL-5.0.3. The driver will treat
BIT(1-8) as the JDBC standard BIT type (which maps to
java.lang.Boolean), as the server does not currently send enough
information to determine the size of a bitfield when < 9 bits are
declared. BIT(>9) will be treated as VARBINARY, and will return
byte[] when getObject() is called.
- --
Mark Matthews
MySQL AB, Software Development Manager - Client Connectivity
www.mysql.com
MySQL User Conference (Santa Clara CA, 18-21 April 2005)
Early registration until February 28: http://www.mysqluc.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCF1OptvXNTca6JD8RAqkhAKDA7sp/iIfCXWn1X/0+ES8wNHNKVQCbBKLn
pPKRJrxovxUOV9W2g0A5zug=
=FJSF
-----END PGP SIGNATURE-----
| Thread |
|---|
| • MySQL Connector/J 3.1.7 Has Been Released | Mark Matthews | 19 Feb |