JDBC Reference
Page 6 of 31

java.sql.Connection

A Cloudscape Connection object is not garbage-collected until all other JDBC objects created from that connection are explicitly closed or are themselves garbage-collected. Once the connection is closed, no further JDBC requests can be made against objects created from the connection. Do not explicitly close the Connection object until you no longer need it for executing statements.

A session-severity or higher exception causes the connection to close and all other JDBC objects against it to be closed. System-severity exceptions cause the Cloudscape system to shut down, which not only closes the connection but means that no new connections should be created in the current JVM.

java.sql.Connection.setTransactionIsolation

Only java.sql.Connection.TRANSACTION_SERIALIZABLE and java.sql.Connection.TRANSACTION_READ_COMMITTED transaction isolations are available from a Cloudscape database; attempting to set isolation to another raises an SQLException.

TRANSACTION_READ_COMMITTED is the default isolation level.

Changing the current isolation for the connection with setConnection commits the current transaction and begins a new transaction, per the JDBC standard.

java.sql.Connection.setReadOnly

java.sql.Connection.setReadOnly is supported.

java.sql.Connection.isReadOnly

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 Cloudscape properties), and Connections to databases on read-only media return true.

Connection Functionality Not Supported

Cloudscape does not use catalog names; the getCatalog and setCatalog methods result in a "Feature not implemented" SQLException with an SQLState of XJZZZ.