Used as a key for caching callable statements which (may) depend on
current catalog...In 5.0.x, they don't (currently), but stored
procedure names soon will, so current catalog is a (hidden) component
of the name.
Thrown when a client requests a connection-level feature
that isn't available for this particular distribution of
Connector/J (currently only used by code that is export-controlled).
Implement this interface, and pass the class name as the
'propertiesTransform' property in your JDBC URL, and the driver
will pass the properties it has parsed to your transform
implementation so that you can modify/substitute/add any that you
desire.
JDBC 2.0 The cancelRowUpdates() method may be called after calling an
updateXXX() method(s) and before calling updateRow() to rollback the
updates made to a row.
JDBC 2.0 The cancelRowUpdates() method may be called after calling an
updateXXX() method(s) and before calling updateRow() to rollback the
updates made to a row.
In some cases, it is desirable to immediately release a Connection's
database and JDBC resources instead of waiting for them to be
automatically released (cant think why off the top of my head)
Note: A Connection is automatically closed when it is garbage
collected.
In some cases, it is desirable to immediately release a ResultSet
database and JDBC resources instead of waiting for this to happen when
it is automatically closed.
In many cases, it is desirable to immediately release a Statement's
database and JDBC resources instead of waiting for this to happen when
it is automatically closed.
The method commit() makes all changes made since the previous
commit/rollback permanent and releases any database locks currently
held by the Connection.
Wraps output from EscapeProcessor, to help prevent multiple passes over
the query string, to detect characters such as '@' (defining/using a
variable), which are used further up the call stack to handle failover.
Some prepared statements return multiple results; the execute method
handles these complex statements as well as the simpler form of
statements handled by executeQuery and executeUpdate
Get a description of the foreign key columns in the foreign key table
that reference the primary key columns of the primary key table
(describe how one table imports another's key.) This should normally
return a single foreign key/primary key pair (most tables only import a
foreign key from a table once.) They are ordered by FKTABLE_CAT,
FKTABLE_SCHEM, FKTABLE_NAME, and KEY_SEQ.
The maxFieldSize limit (in bytes) is the maximum amount of data returned
for any column value; it only applies to BINARY, VARBINARY,
LONGVARBINARY, CHAR, VARCHAR and LONGVARCHAR columns.
A connection's database is able to provide information describing its
tables, its supported SQL grammar, its stored procedures, the
capabilities of this connection, etc.
The getPropertyInfo method is intended to allow a generic GUI tool to
discover what properties it should prompt a human for in order to get
enough information to connect to a database.
Initializes driver properties that come from a JNDI reference (in the
case of a javax.sql.DataSource bound into some name service that
doesn't handle Java objects directly).
Is the column automatically numbered (and thus read-only) MySQL
Auto-increment columns are not read only, so to conform to the spec,
this method returns false.
Can the column be used in a WHERE clause? Basically for this, I split
the functions into two types: recognised types (which are always
useable), and OTHER types (which may or may not be useable).
Used to indicate that the server sent no field-level
character set information, so the driver should use
the connection-level character encoding instead.
Driver that opens two connections, one two a replication master,
and another to one or more slaves, and decides to use master when
the connection is not read-only, and use slave(s) when the connection
is read-only.
A driver may convert the JDBC sql grammar into its system's native SQL
grammar prior to sending it; nativeSQL returns the native form of the
statement that the driver would have sent.
A ResultSet is initially positioned before its first row, the first call
to next makes the first row the current row; the second call makes the
second row the current row, etc.
A ResultSet is initially positioned before its first row, the first call
to next makes the first row the current row; the second call makes the
second row the current row, etc.
Objects that want to be notified of lifecycle events on a
WatchableOutputStream should implement this interface,
and register themselves with setWatcher() on the WatchableOutputStream
instance.
Parses hostPortPair in the form of [host][:port] into an array, with the
element of index HOST_NAME_INDEX being the host (or null if not
specified), and the element of index PORT_NUMBER_INDEX being the port
(or null if not specified).
The prev method is not part of JDBC, but because of the architecture of
this driver it is possible to move both forward and backward within the
result set.
The prev method is not part of JDBC, but because of the architecture of
this driver it is possible to move both forward and backward within the
result set.
Connection that opens two connections, one two a replication master,
and another to one or more slaves, and decides to use master when
the connection is not read-only, and use slave(s) when the connection
is read-only.
Given a ResultSet and an index into the columns of that ResultSet,
read binary data from the column which represents a serialized object,
and re-create the object.
You can put a connection in read-only mode as a hint to enable database
optimizations Note: setReadOnly cannot be called while in the
middle of a transaction
Determines whether or not the string 'searchIn' contains the string
'searchFor', dis-regarding case starting at 'startAt' Shorthand for a
String.regionMatch(...)
If table correlation names are supported, are they restricted to be
different from the names of the tables? A JDBC compliant driver always
returns true.
The JDBC driver will call this method if the user has loaded your
implementation of this interface by specifying the 'propertiesTransform'
property in their JDBC URL.
Objects that want to be notified of lifecycle events on a
WatchableWriter should implement this interface,
and register themselves with setWatcher() on the WatchableWriter
instance.