List:MySQL and Java« Previous MessageNext Message »
From:Mark Matthews Date:October 20 2006 8:18pm
Subject:MySQL Connector/J 5.0.4 Has Been Released
View as plain text  
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

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

This is a bugfix release for the current production branch of Connector/J.

Version 5.0.4 is suitable for use with any MySQL version including
MySQL-4.1, MySQL-5.0 or MySQL-5.1 beta.

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

As always, we recommend that you check the change log
(http://dev.mysql.com/doc/refman/5.0/en/cj-news.html) and "Upgrading"
sections (http://dev.mysql.com/doc/refman/5.0/en/cj-upgrading.html) in
the manual before upgrading to be aware of changes in behavior that
might affect your application.

	-Mark

- From the change log (notice that this release includes changes and
fixes from versions 3.1.14 and the yet-to-be-released 3.1.15 versions):

10-20-06 - Version 5.0.4

    - Fixed BUG#21379 - column names don't match metadata in cases where
server doesn't return original column names (column functions) thus
reaking compatibility with applications that expect 1-1 mappings between
findColumn() and rsmd.getColumnName(), usually manifests itself as
"Can't find column ('')" exceptions.
	
    - Fixed BUG#21544 - When using information_schema for metadata,
COLUMN_SIZE for getColumns() is not clamped to range of
java.lang.Integer as is the case when not using information_schema, thus
leading to a truncation exception that isn't present when not using
information_schema.
	
    - Fixed configuration property "jdbcCompliantTruncation" was not
being used for reads of result set values.

    - Fixed BUG#22024 - Newlines causing whitespace to span confuse
procedure parser when getting parameter metadata for stored procedures.
	
    - Driver now supports {call sp} (without "()" if procedure has no
arguments).
	
    - Fixed BUG#22359 - Driver was using milliseconds for
Statement.setQueryTimeout() when specification says argument is to be in
seconds.
	
    - Workaround for server crash when calling stored procedures via a
server-side prepared statement (driver now detects prepare(stored
procedure) and substitutes client-side prepared statement), addresses
BUG#22297.
	
    - Added new _ci collations to CharsetMapping, fixing  Bug#22456 -
utf8_unicode_ci not working.
	
    - Fixed BUG#22290 - Driver issues truncation on write exception when
it shouldn't (due to sending big decimal incorrectly to server with
server-side prepared statement).
	
    - Fixed BUG#22613 - DBMD.getColumns() does not return expected
COLUMN_SIZE for the SET type, now returns length of largest possible
set disregarding whitespace or the "," delimitters to be consistent
with the ODBC driver.
	
    - Driver now sends numeric 1 or 0 for client-prepared statement
setBoolean() calls instead of '1' or '0'.
	
    - DatabaseMetaData correctly reports true for supportsCatalog*()
methods.

nn-nn-06 - Version 3.1.15

    - Fixed BUG#23281 - Downed slave caused round-robin load balance to
  not cycle back to first host in list.
	
10-19-06 - Version 3.1.14

    - Fixed BUG#20479 - Updatable result set throws ClassCastException
when there is row data and moveToInsertRow() is called.
	
    - Fixed BUG#20485 - Updatable result set that contains a BIT column
fails when server-side prepared statements are used.
	
    - Fixed BUG#16987 - Memory leak with profileSQL=true.
	
    - Fixed BUG#19726 - Connection fails to localhost when using
timeout and IPv6 is configured.
	
    - Fixed BUG#16791 - NullPointerException in MysqlDataSourceFactory
due to Reference containing RefAddrs with null content.
	
    - Fixed BUG#20306 - ResultSet.getShort() for UNSIGNED TINYINT	
returns incorrect values when using server-side prepared statements.
	
    - Fixed BUG#20687 - Can't pool server-side prepared statements,
exception raised when re-using them.
	
    - Fixed BUG#21062 - ResultSet.getSomeInteger() doesn't work for BIT(>1).
	
    - Fixed BUG#18880 - ResultSet.getFloatFromString() can't retrieve	
values near Float.MIN/MAX_VALUE.
	
    - Fixed BUG#20888 - escape of quotes in client-side prepared 	
statements parsing not respected. Patch covers more than bug report, 	
including NO_BACKSLASH_ESCAPES being set, and stacked quote characters	
 forms of escaping (i.e. '' or "").
	
    - Fixed BUG#19993 - ReplicationDriver does not always round-robin
load balance depending on URL used for slaves list.
	
    - Fixed calling toString() on ResultSetMetaData for driver-generated
(i.e. from DatabaseMetaData method calls, or from getGeneratedKeys())	
result sets would raise a NullPointerException.
	
    - Fixed Bug#21207 - Driver throws NPE when tracing prepared
satements that have been closed (in asSQL()).
	
    - Removed logger autodectection altogether, must now specify logger
 explicitly if you want to use a logger other than one that logs to STDERR.
	
    - Fixed BUG#22290 - Driver issues truncation on write exception when
it shouldn't (due to sending big decimal incorrectly to server with
server-side prepared statement).
	
    - Driver now sends numeric 1 or 0 for client-prepared statement
setBoolean() calls instead of '1' or '0'.
	
    - Fixed bug where driver would not advance to next host if
roundRobinLoadBalance=true and the last host in the list is down.

    - Fixed BUG#18258 - DatabaseMetaData.getTables(), columns() with bad
catalog parameter threw exception rather than return empty result set
(as required by spec).
	
    - Check and store value for continueBatchOnError property in
constructor of Statements, rather than when executing batches, so that
Connections closed out from underneath statements don't cause
NullPointerExceptions when it's required to check this property.

    - Fixed BUG#21814 - time values outside valid range silently wrap.
	       	  	
    - Fixed bug when calling stored functions, where parameters weren't
numbered correctly (first parameter is now the return value, subsequent
parameters if specified start at index "2").

    - Fixed BUG#21814 - time values outside valid range silently wrap.

- --
Mark Matthews
MySQL AB, Software Development Manager - Client Connectivity
www.mysql.com


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (MingW32)

iD8DBQFFOS8OtvXNTca6JD8RAttIAKCZ+FHp4R3K5ZQyXSvOQB78IkGsaACeLoCc
yT2opRUxa/uv1IqhDUkAs0Q=
=F1H5
-----END PGP SIGNATURE-----
Thread
MySQL Connector/J 5.0.4 Has Been ReleasedMark Matthews20 Oct