Connection

A constant indicating that transactions are not supported.

No dirty reads are permitted, therefore transactions may not read a row containing uncommitted values - but does not prevent an application from non-repeatable reads and phantom reads.

In the case that reading uncommitted values is allowed, the following incidents may happen which may lead to an invalid results:

• dirty reads
• non-repeatable reads
• phantom reads

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

The constant that indicates that the following incidents are all prevented (the opposite of TRANSACTION_READ_UNCOMMITTED):

• dirty reads
• non-repeatable reads
• phantom reads

Discards all warnings that may have arisen for this connection. Subsequent calls to getWarnings() will return null up until a 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 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 finalize method of the connection closes the connection before garbage collection takes place, it is not advisable to leave the close operation to take place in this way. Mainly because undesired side-effects may appear.

Commits all of the changes made since 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 leads to 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 have the characteristics specified in the type and concurrency 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 ResultSet.TYPE_FORWARD_ONLY and concurrency level ResultSet.CONCUR_READ_ONLY.

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

Gets this Connection object's current catalog name.

Returns the holdability property that any ResultSet produced by 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 transaction isolation level for this connection.

Returns the type mapping associated with this Connection object. The type mapping must be set on the application level.

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 of this connection's warning objects.

Returns a boolean indicating 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 indicating whether or not this connection is currently in the 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 tell the driver whether such keys should be made accessible. This is only relevant when the sql statement 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 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 SQLExceptions 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 handling 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 concurrency mode.

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. 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 SQLExceptions 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, the 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. 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 SQLExceptions get raised.

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

Releases the specified 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 and relinquishes 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 are run and committed as separate transactions. By contrast, setting auto-commit 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 completed 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 the 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.