Added support for Connector/MXJ integration using url
Idle timeouts cause
XAConnections to whine
about rolling themselves back.
When fix for Bug #14562 was merged from 3.1.12, added
parameter metadata to return correct information for
Add one level of indirection of internal representation of
CallableStatement parameter metadata to avoid
class not found issues on JDK-1.3 for
ParameterMetadata interface (which doesn't
exist prior to JDBC-3.0).
Added service-provider entry to
Fuller synchronization of
Connection to avoid
deadlocks when using multi-threaded frameworks that multi-thread
a single connection (usually not recommended, but the JDBC spec
permits it anyways), part of fix to Bug #14972).
(it is not the default) causes the driver to use GMT for
time zones, and the current VM time zone for any other type that
refers to time zones. This feature can not be used when
useTimezone=true to convert between server
and client time zones.
SQLException constructor usage to a
SQLError (ground-work for JDBC-4.0
SQLState-based exception classes).
Return original column name for
RSMD.getColumnName() if the column was
aliased, alias name for
aliased), and original table name for
.getTableName(). Note this only works for
MySQL-4.1 and newer, as older servers don't make this
information available to clients.
-bin-g.jar file into separate
debug subdirectory to avoid confusion.
Removed Java5-specific calls to
constructor (when result set value is
(int)0 was being used as an argument
indirectly using method return value. This signature doesn't
exist prior to Java5.)
XADataSource implemented (ported from 3.2
branch which won't be released as a product). Use
as your datasource class name in your application server to
utilize XA transactions in MySQL-5.0.10 and newer.
Statement.setQueryTimeout(). Both require
MySQL-5.0.0 or newer server, require a separate connection to
QUERY statement, and in the case of
setQueryTimeout() creates an additional
thread to handle the timeout functionality.
Note: Failures to cancel the statement for
setQueryTimeout() may manifest themselves as
RuntimeExceptions rather than failing
silently, as there is currently no way to unblock the thread
that is executing the query being cancelled due to timeout
expiration and have it throw the exception instead.
Do not permit
on an XA-managed connection as per the JDBC specification.
If the connection
useTimezone is set to
true, then also respect time zone conversions
in escape-processed string literals (for example,
Return "[VAR]BINARY" for
RSMD.getColumnTypeName() when that is
actually the type, and it can be distinguished (MySQL-4.1 and
Added unit tests for
XADatasource, as well as
friendlier exceptions for XA failures compared to the "stock"
XAException (which has no messages).
Attempt detection of the MySQL type
BINARY (it is an alias, so this
isn't always reliable), and use the
java.sql.Types.BINARY type mapping for it.