+

Search Tips   |   Advanced Search

JDBC application cursor holdability support

The cursor holdability feature can reduce the overhead of JDBC interaction with your relational database, thereby helping to increase application performance.

By activating cursor holdability, you keep a result set available across transaction boundaries for use by multiple JDBC calls. The holdability setting triggers a database cursor to keep newly updated rows active beyond the commit of the transaction that generated the new values, or result set. Hence the cursor makes the result set available for use by statements in a subsequent transaction.


Set cursor holdability

Using one of the following techniques to set cursor holdability. For more details, see the JDBC 3.0 specification, available at the Oracle website at http://www.oracle.com/technetwork/java/index.html.


The impact of connection and transaction behaviors on cursor holdability

Set cursor holdability in WebSphere Application Server results in the following behavior for different transaction events:

For a global transaction with an unshareable connection, the backend database has responsibility for supporting cursor holdability.

  • Custom property settings