null as a parameter.
Actually write manifest file to correct place so it ends up in the binary jar file. (Bug #10144)
Try to handle
gracefully. Although not much can be done, they will in most
cases close the connection they happened on so that further
operations don't run into a connection in some unknown state.
When an OOM has happened, any further operations on the
connection will fail with a “Connection closed”
exception that will also list the OOM exception as the reason
for the implicit connection close event.
autoReconnect ping causes exception on
Reorganized directory layout. Sources now are in
src folder. Don't pollute parent directory
when building, now output goes to
distribution goes to
Overhaul of character set configuration, everything now lives in a properties file.
Connection.setCatalog() is now aware of the
useLocalSessionState configuration property,
which when set to
true will prevent the
driver from sending
USE ... to the server if
the requested catalog is the same as the current catalog.
cachePrepStmts=true now causes the
Connection to also cache the check the driver
performs to determine if a prepared statement can be server-side
or not, as well as caches server-side prepared statements for
the lifetime of a connection. As before, the
prepStmtCacheSize parameter controls the size
of these caches.
COM_RESET_STMT for each execution
of a server-side prepared statement if it isn't required.
3-0-Compat: Compatibility with Connector/J
Production package doesn't include JBoss integration classes. (Bug #11411)
maxPerformance: Maximum performance without
SMALLINT treated as
ResultSet.getInt(), fixed all
UNSIGNED integer values and
server-side prepared statements, as well as
solarisMaxPerformance: Maximum performance
for Solaris, avoids syscalls where it can
property (defaults to
true), which tells the
driver whether or not to keep track of the last query time and
the last successful packet sent to the server's time. If set to
false, removes two syscalls per query.
0-length streams not sent to server when using server-side prepared statements. (Bug #10850)
The data type returned for
tinyInt1isBit=true (the default) can be
Types.BIT using the new configuration
false. If set to
false (the default),
ResultSetMetaData.getColumnType() will return
TINYINT(1) columns. If
be returned instead. Regardless of this configuration property,
tinyInt1isBit is enabled, columns with the
TINYINT(1) will be returned as
java.lang.Boolean instances from
VARBINARY data corrupted when
using server-side prepared statements and
false), which will cause the
driver to ask the server to create the database specified in the
URL if it doesn't exist. You must have the appropriate
privileges for database creation for this to work.
SQLException thrown when retrieving
ResultSet.getString(). The driver will now
YEAR types as
java.sql.Dates and return the correct values
getString(). Alternatively, the
yearIsDateType connection property can be set
false and the values will be treated as
Connector/J dumping query into
correctly so auto-explain functionality would work with
server-side prepared statements.
Double quotation marks not recognized when parsing client-side prepared statements. (Bug #10155)
Removed nonsensical “costly type conversion” warnings when using usage advisor. (Bug #11411)
does unnecessary call to
Driver doesn't support
calling stored functions. This involved adding support for
function retrieval to
getProcedureColumns() as well.
Memory leak in
Added support/bug hunting feature that generates
.sql test scripts to
autoGenerateTestcaseScript is set to
Driver detects if you're running MySQL-5.0.7 or later, and does
not scan for
LIMIT ?[,?] in statements being
prepared, as the server supports those types of queries now.
SQLException is thrown when using property
Made JDBC2-compliant wrappers public to enable access to vendor extensions. (Bug #10155)
Added the following configuration bundles, use one or many using
useConfigs configuration property:
maxPerformance: Maximum performance
without being reckless
performance for Solaris, avoids syscalls where it can
3-0-Compat: Compatibility with
Connector/J 3.0.x functionality
true. The driver has supported
this for some time, DBMD just missed that fact.
Cleaned up logging of profiler events, moved code to dump a
profiler event as a string to
com.mysql.jdbc.log.LogUtils so that third
parties can use it.
enableStreamingResults() visible on
Driver now correctly uses CP932 if available on the server for Windows-31J, CP932 and MS932 java encoding names, otherwise it resorts to SJIS, which is only a close approximation. Currently only MySQL-5.0.3 and newer (and MySQL-4.1.12 or .13, depending on when the character set gets backported) can reliably support any variant of CP932.