Methods Summary |
---|
public void | clearWarnings()Discards all warnings that may have arisen for this connection.
Subsequent calls to {@link #getWarnings()} will return {@code null}
up until a new warning condition occurs.
|
public void | close()Causes the instant release of all database and driver connection
resources associated with this object. Any subsequent invocations of this
method have no effect.
It is strongly recommended that all connections are closed before they
are dereferenced by the application ready for garbage collection.
Although the {@code finalize} method of the connection closes the
connection before garbage collection takes place, it is not advisable to
leave the {@code close} operation to take place in this way. Mainly
because undesired side-effects may appear.
|
public void | commit()Commits all of the changes made since the last {@code commit} or
{@code rollback} of the associated transaction. All locks in the database
held by this connection are also relinquished. Calling this operation on
connection objects in {@code auto-commit} mode leads to an error.
|
public java.sql.Statement | createStatement()Returns a new instance of {@code Statement} for issuing SQL commands to
the remote database.
{@code ResultSets} generated by the returned statement will default to
type {@code ResultSet.TYPE_FORWARD_ONLY} and concurrency level {@code
ResultSet.CONCUR_READ_ONLY}.
|
public java.sql.Statement | createStatement(int resultSetType, int resultSetConcurrency)Returns a new instance of {@code Statement} whose associated {@code
ResultSet}s have the characteristics specified in the type and
concurrency arguments.
|
public java.sql.Statement | createStatement(int resultSetType, int resultSetConcurrency, int resultSetHoldability)Returns a new instance of {@code Statement} whose associated
{@code ResultSet}s will have the characteristics specified in the
type, concurrency and holdability arguments.
|
public boolean | getAutoCommit()Returns a {@code boolean} indicating whether or not this connection is in
the {@code auto-commit} operating mode.
|
public java.lang.String | getCatalog()Gets this {@code Connection} object's current catalog name.
|
public int | getHoldability()Returns the holdability property that any {@code ResultSet} produced by
this instance will have.
|
public java.sql.DatabaseMetaData | getMetaData()Gets the metadata about the database referenced by this connection. The
returned {@code DatabaseMetaData} describes the database topography,
available stored procedures, SQL syntax and so on.
|
public int | getTransactionIsolation()Returns the transaction isolation level for this connection.
|
public java.util.Map | getTypeMap()Returns the type mapping associated with this {@code Connection} object.
The type mapping must be set on the application level.
|
public java.sql.SQLWarning | getWarnings()Gets the first instance of any {@code SQLWarning} objects that may have
been created in the use of this connection. If at least one warning has
occurred then this operation returns the first one reported. A {@code
null} indicates that no warnings have occurred.
By invoking the {@link SQLWarning#getNextWarning()} method of the
returned {@code SQLWarning} object it is possible to obtain all of
this connection's warning objects.
|
public boolean | isClosed()Returns a {@code boolean} indicating whether or not this connection is in
the {@code closed} state. The {@code closed} state may be entered into as
a consequence of a successful invocation of the {@link #close()} method
or else if an error has occurred that prevents the connection from
functioning normally.
|
public boolean | isReadOnly()Returns a {@code boolean} indicating whether or not this connection is
currently in the {@code read-only} state.
|
public java.lang.String | nativeSQL(java.lang.String sql)Returns a string representation of the input SQL statement
{@code sql} expressed in the underlying system's native SQL
syntax.
|
public java.sql.CallableStatement | prepareCall(java.lang.String sql)Returns a new instance of {@code CallableStatement} that may be used for
making stored procedure calls to the database.
|
public java.sql.CallableStatement | prepareCall(java.lang.String sql, int resultSetType, int resultSetConcurrency)Returns a new instance of {@code CallableStatement} that may be used for
making stored procedure calls to the database. {@code ResultSet}s emitted
from this {@code CallableStatement} will satisfy the specified {@code
resultSetType} and {@code resultSetConcurrency} values.
|
public java.sql.CallableStatement | prepareCall(java.lang.String sql, int resultSetType, int resultSetConcurrency, int resultSetHoldability)Returns a new instance of {@code CallableStatement} that may be used for
making stored procedure calls to the database. {@code ResultSet}s created
from this {@code CallableStatement} will have characteristics determined
by the specified type, concurrency and holdability arguments.
|
public java.sql.PreparedStatement | prepareStatement(java.lang.String sql)Returns a new instance of {@code PreparedStatement} that may be used any
number of times to execute parameterized requests on the database server.
Subject to JDBC driver support, this operation will attempt to send the
precompiled version of the statement to the database. If
the driver does not support precompiled statements, the statement will
not reach the database server until it is executed. This distinction
determines the moment when {@code SQLException}s get raised.
By default, {@code ResultSet}s from the returned object will be
{@link ResultSet#TYPE_FORWARD_ONLY} type with a
{@link ResultSet#CONCUR_READ_ONLY} mode of concurrency.
|
public java.sql.PreparedStatement | prepareStatement(java.lang.String sql, int autoGeneratedKeys)Creates a default {@code PreparedStatement} that can retrieve
automatically generated keys. Parameter {@code autoGeneratedKeys} may be
used to tell the driver whether such keys should be made accessible.
This is only relevant when the {@code sql} statement is an {@code insert}
statement.
An SQL statement which may have {@code IN} parameters can be stored and
precompiled in a {@code PreparedStatement}. The {@code PreparedStatement}
can then be then be used to execute the statement multiple times in an
efficient way.
Subject to JDBC driver support, this operation will attempt to send the
precompiled version of the statement to the database. If
the driver does not support precompiled statements, the statement will
not reach the database server until it is executed. This distinction
determines the moment when {@code SQLException}s get raised.
By default, {@code ResultSet}s from the returned object will be
{@link ResultSet#TYPE_FORWARD_ONLY} type with a
{@link ResultSet#CONCUR_READ_ONLY} mode of concurrency.
|
public java.sql.PreparedStatement | prepareStatement(java.lang.String sql, int[] columnIndexes)Creates a default {@code PreparedStatement} that can retrieve the
auto-generated keys designated by a supplied array. If {@code sql} is an
SQL {@code INSERT} statement, the parameter {@code columnIndexes} is expected
to hold the index values for each column in the statement's intended
database table containing the autogenerated-keys of interest. Otherwise
{@code columnIndexes} is ignored.
Subject to JDBC driver support, this operation will attempt to send the
precompiled version of the statement to the database. If
the driver does not support precompiled statements, the statement will
not reach the database server until it is executed. This distinction
determines the moment when {@code SQLException}s get raised.
By default, {@code ResultSet}s from the returned object will be
{@link ResultSet#TYPE_FORWARD_ONLY} type with a
{@link ResultSet#CONCUR_READ_ONLY} concurrency mode.
|
public java.sql.PreparedStatement | prepareStatement(java.lang.String sql, int resultSetType, int resultSetConcurrency)Creates a {@code PreparedStatement} that generates {@code ResultSet}s
with the specified values of {@code resultSetType} and {@code
resultSetConcurrency}.
|
public java.sql.PreparedStatement | prepareStatement(java.lang.String sql, int resultSetType, int resultSetConcurrency, int resultSetHoldability)Creates a {@code PreparedStatement} that generates {@code ResultSet}s
with the specified type, concurrency and holdability
|
public java.sql.PreparedStatement | prepareStatement(java.lang.String sql, java.lang.String[] columnNames)Creates a default {@code PreparedStatement} that can retrieve the
auto-generated keys designated by a supplied array. If {@code sql} is an
SQL {@code INSERT} statement, {@code columnNames} is expected to hold the
names of each column in the statement's associated database table
containing the autogenerated-keys of interest. Otherwise {@code
columnNames} is ignored.
Subject to JDBC driver support, this operation will attempt to send the
precompiled version of the statement to the database. Alternatively, if
the driver is not capable of handling precompiled statements, the
statement will not reach the database server until it is executed. This
will have a bearing on precisely when {@code SQLException}
instances get raised.
By default, ResultSets from the returned object will be
{@link ResultSet#TYPE_FORWARD_ONLY} type with a
{@link ResultSet#CONCUR_READ_ONLY} concurrency mode.
|
public void | releaseSavepoint(java.sql.Savepoint savepoint)Releases the specified {@code savepoint} from the present transaction. Once removed,
the {@code Savepoint} is considered invalid and should not be referenced
further.
|
public void | rollback()Rolls back all updates made so far in this transaction and
relinquishes all acquired database locks. It is an error to invoke this
operation when in auto-commit mode.
|
public void | rollback(java.sql.Savepoint savepoint)Undoes all changes made after the supplied {@code Savepoint} object was
set. This method should only be used when auto-commit mode is disabled.
|
public void | setAutoCommit(boolean autoCommit)Sets this connection's auto-commit mode {@code on} or {@code off}.
Putting a Connection into auto-commit mode means that all associated SQL
statements are run and committed as separate transactions.
By contrast, setting auto-commit to {@code off} means that associated SQL
statements get grouped into transactions that need to be completed by
explicit calls to either the {@link #commit()} or {@link #rollback()}
methods.
Auto-commit is the default mode for new connection instances.
When in this mode, commits will automatically occur upon successful SQL
statement completion or upon successful completion of an execute.
Statements are not considered successfully completed until all associated
{@code ResultSet}s and output parameters have been obtained or closed.
Calling this operation during an uncommitted transaction will result in
it being committed.
|
public void | setCatalog(java.lang.String catalog)Sets the catalog name for this connection. This is used to select a
subspace of the database for future work. If the driver does not support
catalog names, this method is ignored.
|
public void | setHoldability(int holdability)Sets the holdability of the {@code ResultSet}s created by this Connection.
|
public void | setReadOnly(boolean readOnly)Sets this connection to read-only mode.
This serves as a hint to the driver, which can enable database
optimizations.
|
public java.sql.Savepoint | setSavepoint()Creates an unnamed {@code Savepoint} in the current transaction.
|
public java.sql.Savepoint | setSavepoint(java.lang.String name)Creates a named {@code Savepoint} in the current transaction.
|
public void | setTransactionIsolation(int level)Sets the transaction isolation level for this Connection.
If this method is called during a transaction, the results are
implementation defined.
|
public void | setTypeMap(java.util.Map map)Sets the {@code TypeMap} for this connection. The input {@code map}
should contain mappings between complex Java and SQL types.
|