JDBC3 + HOLD_CURSORS_OVER_COMMIT

It occurred to me that we can support JDBC3's HOLD_CURSORS_OVER_COMMIT
behaviour quite simply by doing the same thing we do with scrollable
resultsets -- disable use of cursors entirely.

Does this sound worth doing? Obviously we could replace it with proper
WITH HOLD cursor-backed resultsets eventually..

-O