Oracle 5.0 Reference Manual page 2094

• The must cover all columns that make up the primary key.
SELECT
The BLOB implementation does not allow in-place modification (they are copies, as reported
by the
DatabaseMetaData.locatorsUpdateCopies()
corresponding
PreparedStatement.setBlob()
updatable result sets) methods to save changes back to the database.
• CallableStatement
Starting with Connector/J 3.1.1, stored procedures are supported when connecting to
MySQL version 5.0 or newer using the
getParameterMetaData()
• CLOB
The CLOB implementation does not allow in-place modification (they are copies, as reported
by the
DatabaseMetaData.locatorsUpdateCopies()
PreparedStatement.setClob()
does not have a
ResultSet.updateClob()
• Connection
Unlike the pre-Connector/J JDBC driver (MM.MySQL), the
server to determine if it is available. In accordance with the JDBC specification, it only returns true if
has been called on the connection. If you need to determine if the connection is still valid,
closed()
issue a simple query, such as
longer valid.
• DatabaseMetaData
Foreign key information
getCrossReference()) is only available from
to retrieve this information, so if any other storage engines add support for foreign keys, the
TABLE
driver would transparently support them as well.
• PreparedStatement
PreparedStatements are implemented by the driver, as MySQL does not have a prepared
statement feature. Because of this, the driver does not implement
as it would require the driver to have a complete SQL parser in the client.
getMetaData()
Starting with version 3.1.0 MySQL Connector/J, server-side prepared statements and binary-
encoded result sets are used when the server supports them.
Take care when using a server-side prepared statement with large parameters that are set
using setBinaryStream(), setAsciiStream(), setUnicodeStream(), setBlob(),
or setClob(). To re-execute the statement with any large parameter changed to a nonlarge
parameter, call
clearParameters()
follows:
• During both server-side prepared statements and client-side emulation, large data is exchanged
only when
PreparedStatement.execute()
• Once that has been done, the stream used to read the data on the client side is closed (as per the
JDBC spec), and cannot be read from again.
• If a parameter changes from large to nonlarge, the driver must reset the server-side state of
the prepared statement to allow the parameter that is being changed to take the place of the
prior large value. This removes all of the large data that has already been sent to the server,
Connector/J (JDBC) Reference
CallableStatement
method of
CallableStatement
method to save changes back to the database. The JDBC API
1. The driver will throw an exception if the connection is no
SELECT
(getImportedKeys()/getExportedKeys()
and set all parameters again. The reason for this is as
2074
method). Because of this, use the
or
ResultSet.updateBlob()
interface. Currently, the
is not supported.
method). Because of this, use the
method.
isClosed()
tables. The driver uses
InnoDB
getParameterMetaData()
is called.
(in the case of
method does not ping the
and
SHOW CREATE
or