ServerPreparedStatement to read
prepared statement metadata off the wire, even though it is
currently a placeholder instead of using
MysqlIO.clearInputStream() which didn't work
at various times because data wasn't available to read from the
server yet. This fixes sporadic errors users were having with
Added three ways to deal with all-zero datetimes when reading
them from a
exception (the default), which throws an
SQLException with an SQLState of
NULL instead of the date; and
round, which rounds the date to the nearest
closest value which is
The driver is more strict about truncation of numerics on
ResultSet.get*(), and will throw an
SQLException when truncation is detected. You
can disable this by setting
false (it is enabled by default, as this
functionality is required for JDBC compliance).
You can now use URLs in
LOAD DATA LOCAL
INFILE statements, and the driver will use Java's
built-in handlers for retrieving the data and sending it to the
server. This feature is not enabled by default, you must set the
allowUrlInLocalInfile connection property to
ResultSet.getObject() doesn't return type
Boolean for pseudo-bit types from prepared
statements on 4.1.x (shortcut for avoiding extra type conversion
when using binary-encoded result sets obscured test in
getObject() for “pseudo” bit
com.mysql.jdbc.Message's classloader when
loading resource bundle, should fix sporadic issues when the
caller's classloader can't locate the resource bundle.
ServerPreparedStatements dealing with return
DECIMAL type don't work.
Track packet sequence numbers if
enablePacketDebug=true, and throw an
exception if packets received out-of-order.
ResultSet.wasNull() does not work for
primitives if a previous
null was returned.
Optimized integer number parsing, enable “old”
slower integer parsing using JDK classes using
which causes message text in exceptions generated by the server
to only contain the text sent by the server (as opposed to the
SQLState's “standard” description, followed by the
server's error message). This property is set to
true by default.
unpacking field metadata.
Connector/J 3.1.3 beta does not handle integers correctly
(caused by changes to support unsigned reads in
Added support in
getTableTypes() for views, which are now
available in MySQL server 5.0.x.
ResultSet.getObject() returns wrong type for
strings when using prepared statements.
(even though an application error), caused NPE. Fixed.