> What is not being cached in auto-commit mode?

Currently we fetch complete result set for any type of selects in
auto-commit mode. This was implemented since JDBC 1.2 and 2.0 specs
did not define the statement and result set lifecycle in auto-commit
mode and it was not clear whether we have to support multiple
statements with open result sets or not. JDBC 3.0 filled that gap.

In new version no results will be cached for
ResultSet.TYPE_FORWARD_ONLY (ResultSet.TYPE_SCROLL_INSENSITIVE will be
still cached), you will have only fetchSize kept in memory. Also there
will be only one active statement at a time - according to specs
result set is closed when another statement is executed over the same
connection.

See the rules described in JDBC 3.0 specification in chapter where
auto-commit mode is discussed.

Roman