Connection

A constant indicating that transactions are not supported.

No dirty reads are permitted. Transactions may not read a row containing changes that have not yet been committed.

Dirty reads (reading from table rows containing changes that have not yet been committed), non-repeatable reads (reading table rows more than once in a transaction but getting back different data because other transactions may have altered rows between reads), and phantom reads (retrieving additional "phantom" rows in the course of repeated table reads because other transactions may have inserted additional rows that satisfy an SQL WHERE clause) are all permitted.

A constant indicating that dirty reads and non-repeatable reads are prevented; phantom reads can occur.

Dirty reads (reading from table rows containing changes that have not yet been committed), non-repeatable reads (reading table rows more than once in a transaction but getting back different data because other transactions may have altered rows between reads), and phantom reads (retrieving additional "phantom" rows in the course of repeated table reads because other transactions may have inserted additional rows that satisfy an SQL WHERE clause) are all prevented.

Throws away any warnings that may have arisen for this connection. Subsequent calls to getWarnings() will return null up until a brand new warning condition occurs.

Causes the instant release of all database and driver connection resources associated with this object. Any subsequent invocations of this method will have no effect.

It is strongly recommended that all Connections are closed before they are dereferenced by the application ready for garbage collection. While the finalize method of the Connection will close the Connection before garbage collection takes place, it is not advisable to leave the close operation to take place in this way. Unpredictable performance may result from closing Connections in the finalizer.

Commits all of the changes made subsequent to the last commit or rollback of the associated transaction. All locks in the database held by this connection are also relinquished. Calling this operation on connection objects in auto-commit mode is an error.

Returns a new instance of Statement whose associated ResultSets will have the characteristics specified in the type, concurrency and holdability arguments.

Returns a new instance of Statement whose associated ResultSets will have the characteristics specified in the type, concurrency and holdability arguments.

Returns a new instance of Statement for issuing SQL commands to the remote database.

ResultSets generated by the returned Statement will default to type TYPE_FORWARD_ONLY and concurrency level CONCUR_READ_ONLY.

Returns a boolean indication of whether or not this connection is in the auto-commit operating mode.

Gets this Connection object's current catalog name.

Returns the kind of holdability that any ResultSets made from this instance will have.

Gets the metadata about the database referenced by this connection. The returned DatabaseMetaData describes the database topography, available stored procedures, SQL syntax and so on.

Returns the present value of transaction isolation for this Connection instance.

Returns the Type Map associated with this Connection object. The type map will be empty unless the application has added at least one entry.

Gets the first instance of any 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 null indicates that no warnings have occurred.

By invoking the getNextWarning() method of the returned SQLWarning object it is possible to obtain all warning objects.

Returns a boolean indication of whether or not this connection is in the closed state. The closed state may be entered into as a consequence of a successful invocation of the close() method or else if an error has occurred that prevents the connection from functioning normally.

Returns a boolean indication of whether or not this connection is currently in read-only state.

Returns a string representation of the input SQL statement sql expressed in the underlying system's native SQL syntax.

Returns a new instance of CallableStatement that may be used for making stored procedure calls to the database.

Returns a new instance of CallableStatement that may be used for making stored procedure calls to the database. ResultSets created from this CallableStatement will have characteristics determined by the specified type, concurrency and holdability arguments.

Returns a new instance of CallableStatement that may be used for making stored procedure calls to the database. ResultSets emitted from this CallableStatement will satisfy the specified resultSetType and resultSetConcurrency values.

Creates a default PreparedStatement that can retrieve automatically generated keys. Parameter autoGeneratedKeys may be used to specify to the driver if such keys should be made accessible. This is only the case when sql is an insert statement.

An SQL statement which may have IN parameters can be stored and precompiled in a PreparedStatement. The PreparedStatement can 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. Alternatively, if the driver is not capable of flowing precompiled statements, the statement will not reach the database server until it is executed. This will have a bearing on precisely when SQLException instances get raised.

By default, ResultSets from the returned object will be TYPE_FORWARD_ONLY type with a CONCUR_READ_ONLY mode of concurrency.

Creates a default PreparedStatement that can retrieve the auto-generated keys designated by a supplied array. If sql is an SQL INSERT statement, columnNames is expected to hold the names of each column in the statement's associated database table containing the autogenerated-keys of interest. Otherwise 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 flowing precompiled statements, the statement will not reach the database server until it is executed. This will have a bearing on precisely when SQLException instances get raised.

By default, ResultSets from the returned object will be TYPE_FORWARD_ONLY type with a CONCUR_READ_ONLY mode of concurrency.

Creates a PreparedStatement that generates ResultSets with the specified type, concurrency and holdability

Creates a PreparedStatement that generates ResultSets with the specified values of resultSetType and resultSetConcurrency.

Returns a new instance of 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. Alternatively, if the driver is not capable of flowing precompiled statements, the statement will not reach the database server until it is executed. This will have a bearing on precisely when SQLException instances get raised.

By default, ResultSets from the returned object will be TYPE_FORWARD_ONLY type with a CONCUR_READ_ONLY mode of concurrency.

Creates a default PreparedStatement that can retrieve the auto-generated keys designated by a supplied array. If sql is an SQL INSERT statement, parameter 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 columnIndexes 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 flowing precompiled statements, the statement will not reach the database server until it is executed. This will have a bearing on precisely when SQLException instances get raised.

By default, ResultSets from the returned object will be TYPE_FORWARD_ONLY type with a CONCUR_READ_ONLY mode of concurrency.

Releases savepoint from the present transaction. Once removed, the Savepoint is considered invalid and should not be referenced further.

Undoes all changes made after the supplied Savepoint object was set. This method should only be used when auto-commit mode is disabled.

Rolls back all updates made so far in this transaction as well as relinquishing all acquired database locks. It is an error to invoke this operation when in auto-commit mode.

Sets this connection's auto-commit mode on or off.

Putting a Connection into auto-commit mode means that all associated SQL statements will be run and committed in their own separate transactions. Alternatively, auto-commit set to off means that associated SQL statements get grouped into transactions that need to be completed by explicit calls to either the commit() or 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 complete until all associated ResultSets and output parameters have been obtained or closed.

Calling this operation during an uncommitted transaction will result in it being committed.

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.

Sets the holdability of ResultSets created by this Connection.

Sets this connection to read-only mode.

This serves as a hint to the driver, which can enable database optimizations.

Creates an unnamed Savepoint in the current transaction.

Creates a named Savepoint in the current transaction.

Sets the transaction isolation level for this Connection.

If this method is called during a transaction, the results are implementation defined.

Sets the TypeMap for this connection. The input map should contain mappings between complex Java and SQL types.