MySQL Lists are EOL. Please join:

List:MySQL and Java« Previous MessageNext Message »
From:Mark Matthews Date:October 9 2007 3:25pm
Subject:MySQL Connector/J 5.1.5 Has Been Released!
View as plain text  
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

MySQL Connector/J 5.1.5, the first production release of the 5.1 branch
has been released. Connector/J is the Type-IV pure-Java JDBC driver for
MySQL.

Version 5.1.5 is suitable for use with any MySQL version including
MySQL-4.1, MySQL-5.0, MySQL-5.1 RC or the MySQL-6.0 Falcon development
release.

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 (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 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

This is the first production release of our implementation of the new
JDBC-4.0 API, along with some new performance features.

Notice that there was an internal 5.1.4 release which we didn't publish
because we wanted to pull in a last-minute update from the 5.0 branch
before releasing 5.1 to production.

MySQL Connector/J 5.1.5 includes the following new features compared to
5.1.3:

- - Added "autoSlowLog" configuration property, overrides
"slowQueryThreshold*" properties, driver determines slow      queries by
those that are slower than 5 * stddev of the mean query time (outside
the 96% percentile).

- - Fixed BUG#28256 - When connection is in read-only mode, queries that
are wrapped in parentheses incorrectly identified as DML.

The following features are new, compared to the 5.0 series of Connector/J:

- - JDBC-4.0 ease-of-development features including auto-registration
with the DriverManager via the service provider mechanism, standardized
Connection validity checks and categorized SQLExceptions based on
recoverability/retry-ability and class of the underlying error.

- - JDBC-4.0 standardized unwrapping to interfaces that include vendor
extensions.

- - Support for JDBC-4.0 XML processing via JAXP interfaces to DOM, SAX
and StAX.

- - JDBC-4.0 support for setting per-connection client information
(which can be viewed in the comments section of a query via "SHOW
PROCESSLIST" on a MySQL server, or can be extended to support custom
persistence of the information via a public interface).

- - Support for JDBC-4.0 NCHAR, NVARCHAR and NCLOB types.

- - Added experimental support for statement "interceptors" via the
com.mysql.jdbc.StatementInterceptor interface, examples are in
com/mysql/jdbc/interceptors.  Implement this interface to be placed "in
between" query execution, so that it can be influenced (currently
experimental).

- - Improved connection establishment time by 25% through selective
retrieval of server variables.

- - Improved ResultSet.getString(). It's now twice as fast, compared to 5.0.

- - The driver now picks appropriate internal row representation (whole
row in one buffer, or individual byte[]s for each column value)
depending on heuristics, including whether or not the row has BLOB or
TEXT types and the overall row-size. The threshold for row size that
will cause the driver to use a buffer rather than individual byte[]s is
configured by the configuration property "largeRowSizeThreshold", which
has a default value of 2KB. This change leads to substantial
improvements in memory usage by avoiding copying data or allocating
large blocks of memory when using "streaming" result sets or when
dealing with large rows.

- - Added experimental support for connection lifecycle "interceptors",
which enable notifcation of lifecycle events such as connection
creation, destruction and transaction demarcation and allow code to be
plugged in to influence the behavior of these events, see the source
code of related interfaces at http://tinyurl.com/24g28y and
http://tinyurl.com/29l4xt for more details.

- - The driver will automatically adjust the server session variable
"net_write_timeout" when it determines its been asked for a "streaming"
result, and resets it to the previous value when the result set has been
consumed. (The configuration property is named
"netTimeoutForStreamingResults", with a unit of seconds, the value '0'
means the driver will not try and adjust this value).

- - The data (and how it's stored) for ResultSet rows are now behind an
interface which allows us (in some cases) to allocate less memory per
row, in that for "streaming" result sets, we re-use the packet used to
read rows, since only one row at a time is ever active.

- - Setting "rewriteBatchedStatements" to "true" now causes
CallableStatements with batched arguments to be re-written in the form
"CALL (...); CALL (...); ..." to send the batch in as few client-server
round trips as possible.

This release also includes the following changes that are also present
in Connector/J 5.0.8:

- - Added two configuration parameters (both default to "false")

  * blobsAreStrings  - Should the driver always treat BLOBs as Strings
                                specifically to work around dubious
metadata returned                                  by the server for
GROUP BY clauses?

  * functionsNeverReturnBlobs - Should the driver always treat data from
                                        functions returning BLOBs as
Strings - specifically to work around dubious metadata returned by the
server for GROUP BY clauses?

- - Specifying a "validation query" in your connection pool that starts
with "/* ping */" _exactly_ will cause the driver to instead send a ping
to the server and return a fake result set (much lighter weight), and
when using a ReplicationConnection or a LoadBalancedConnection,
will send the ping across all active connections.

- - XAConnections now start in auto-commit mode (as per JDBC-4.0
specification clarification).

- - Driver will now fall back to sane defaults for max_allowed_packet and
net_buffer_length if the server reports them incorrectly (and will log
    this situation at WARN level, since it's actually an error condition).

- - Fixed BUG#27182 - Connection.getServerCharacterEncoding() doesn't work
     for servers with version >= 4.1.

- - Fixed Bug#27412 - cached metadata with PreparedStatement.execute()
  throws NullPointerException.

- - Fixed BUG#27867 - Schema objects with identifiers other than the
connection character aren't retrieved correctly in      ResultSetMetadata.

- - Fixed BUG#27915 - DatabaseMetaData.getColumns() doesn't contain
SCOPE_* or IS_AUTOINCREMENT columns.

- - Fixed BUG#27916 - UNSIGNED types not reported via DBMD.getTypeInfo(),
and capitalization of type names is not consistent between
DBMD.getColumns(), RSMD.getColumnTypeName() and DBMD.getTypeInfo().

This fix also ensures that the precision of UNSIGNED MEDIUMINT and
UNSIGNED BIGINT is reported correctly via DBMD.getColumns().

- - Fixed BUG#28689 - CallableStatement.executeBatch() doesn't work when
   connection property "noAccessToProcedureBodies" has been set to "true".

The fix involves changing the behavior of "noAccessToProcedureBodies",in
     that the driver will now report all paramters as "IN" paramters but
allow callers to call registerOutParameter() on them without throwing
   an exception.

- - Fixed BUG#28972 - DatabaseMetaData.getTypeInfo() for the types DECIMAL
     and NUMERIC will return a precision of 254 for server versions
older than 5.0.3, 64 for versions 5.0.3-5.0.5 and 65 for versions newer
than 5.0.5.

- - Fixed BUG#29106 - Connection checker for JBoss didn't use same method
parameters via reflection, causing connections to always seem "bad".

- - Fixed BUG#29852 - Closing a load-balanced connection would cause a
  ClassCastException.

- - Fixed BUG#30550, executeBatch() would fail with an ArithmeticException
     and/or NullPointerException when the batch had zero members and
 "rewriteBatchedStatements" was set to "true" for the connection.

- - Fixed BUG#30664 - Note that this fix only works for MySQL server
 versions 5.0.25 and newer, since earlier versions didn't consistently
     return correct metadata for functions, and thus results from
subqueries and functions were indistinguishable from each other,
leading to type-related bugs.

- - Fixed BUG#30851, NPE with null column values when "padCharsWithSpace"
is set to "true".

 - Fixed Bug#30892 setObject(int, Object, int, int) delegate in
PreparedStatmentWrapper delegates to wrong method.

- - Fixed BUG#31053 - Connections established using URLs of the form
"jdbc:mysql:loadbalance://" weren't doing failover if they tried to
connect to a MySQL server that was down. The driver now attempts
connections to the next "best" (depending on the load balance strategy
in use) server, and continues to attempt connecting to the next "best"
server every 250 milliseconds until one is found that is up and running
     or 5 minutes has passed.

If the driver gives up, it will throw the last-received SQLException.


Enjoy!

	-Mark
- --
Mark Matthews, Architect (Enterprise Tools)
MySQL, Inc. Chicago, USA - www.mysql.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHC51atvXNTca6JD8RAiYHAJ93d2W7l4uLecmYwvyTHvZPoBLzSwCgvvns
4RT0jS/JXpsVN7Kzz7CWMN4=
=BJiG
-----END PGP SIGNATURE-----
Thread
MySQL Connector/J 5.1.5 Has Been Released!Mark Matthews9 Oct