When using the Aster Database JDBC driver, you make most behavior and performance settings in your SQL code using the SET command.
You can also use a number of standard JDBC driver methods for setting behavior and performance options, such as setAutoCommit() and setPrepareThreshold().
The scope of these variables are limited to the scope of the transaction. After the commit() call, the transaction variables revert to their original values. In order to limit the transaction variables to a particular query, the variables need to be saved prior to being set and once the query is executed the variables must be set back to their original values.