<< Attributes of the Derby database connection URL | java.sql.DatabaseMetaData interface >>

java.sql.Connection.setTransactionIsolation method

<< Attributes of the Derby database connection URL | java.sql.DatabaseMetaData interface >>

Derby Reference Manual

306

Returns

Signature

Implementation Notes

to an

auto-increment

column within the target
table of the INSERT.
Supported in embedded
mode only.

PreparedStatement

prepareStatement(String sql,
String [] columnNames)

Every column name in
the array must designate
an

auto-increment

column within the target
table of the INSERT.
Supported in embedded
mode only.

See

Autogenerated keys

for details on the use of the two forms of the

Connection.prepareStatement method shown in this table.

java.sql.Connection.setTransactionIsolation method

java.sql.Connection.TRANSACTION_SERIALIZABLE,
java.sql.Connection.TRANSACTION_REPEATABLE_READ,
java.sql.Connection.TRANSACTION_READ_COMMITTED, and
java.sql.Connection.TRANSACTION_READ_UNCOMMITTED transaction isolations are
available from a Derby database.

TRANSACTION_READ_COMMITTED is the default isolation level.

Changing the current isolation for the connection with setTransactionIsolation commits
the current transaction and begins a new transaction. For more details about transaction
isolation, see "Locking, concurrency, and isolation" in the Derby Developer's Guide.

java.sql.Connection.setReadOnly method

java.sql.Connection.setReadOnly is supported.

See the section "Differences using the Connection.setReadOnly method" in the Derby
Server and Administration Guide for more information.

java.sql.Connection.isReadOnly method

If you connect to a read-only database, the appropriate isReadOnly DatabaseMetaData
value is returned. For example, Connections set to read-only using the setReadOnly
method, Connections for which the user has been defined as a readOnlyAccess user
(with one of the Derby properties), and Connections to databases on read-only media
return true.

Connection functionality not supported

Derby does not use catalog names. In addition, the following optional methods raise
"Feature not supported" exceptions:

· createArrayOf( java.lang.String, java.lang.Object[] )
· createNClob( )
· createSQLXML( )
· createStruct( java.lang.String, java.lang.Object[] )
· getTypeMap( )