Timestamp key column data needed
Timestamps converted incorrectly to strings with server-side prepared statements and updatable result sets. (Bug #7715)
sql_mode variable in string
form (it used to be integer) and adjust quoting method for
property (default is
false), that keeps
result sets open over statement.close() or new execution on
same statement (suggested by Kevin Burton).
Infinite recursion when 「falling back」 to master in failover configuration. (Bug #7952)
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
functionality, the driver now always stores results from
server-side prepared statements as is from the server and
unpacks them on demand.
Emulated locators corrupt binary data when using server-side prepared statements. (Bug #8096)
Fixed synchronization issue with
that could cause deadlocks/crashes if connection was shared
By default, the driver now scans SQL you are preparing via
all variants of
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. You can disable this by passing
emulateUnsupportedPstmts=false in your
JDBC URL. (Bug #4718)
_binary introducer from parameters
used as in/out parameters in
bytes for output
parameters registered as
Send correct value for 「boolean」
true to server for
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 time zone
ResultSet.get(..., cal) and
false, to be JDBC compliant),
which helps with memory use for non-well-behaved apps (that
is, applications that don't close
Statement objects when they should).
ResultSet.getString() doesn't maintain
format stored on server, bug fix only enabled when
noDatetimeStringSync property is set to
true (the default is
false). (Bug #8428)
Fixed NPE in
using usage advisor and result set was already closed.
PreparedStatements not creating streaming
result sets. (Bug #8487)
it stringifies it (that is, returns
null), which is not correct for the
method in question.
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. (Bug #8424)
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
and therefore can manipulate these values in many cases
without incurring round-trips to the database server.
Statement for connection pool
implementations that check
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
getObject() is called.