Re: SQL SAVEPOINT command ON ROLLBACK option

On Aug 2, 4:43 pm, "walker.l2" <walker...@xxxxxxxxxxxxxx> wrote:
Hmm, maybe.
I'm worried that neither option seems to fully release SQL resources.
If my program hits an SQL error, I can rollback to the savepoint okay,
but will just doing that release all the SQL resources my program
might have open at the point of the initial error? (Or are these SQL
resources released automatically by the OS when my program ends?)

I suppose I could look into BEGIN ATOMIC ... END instead, but at first
glance SAVEPOINT seemed the simpler solution.

Surely to fully release resources you have to end the work unit with a
final commit, or rollback with no savepoint specified?
It does seem odd that you must specify 'on rollback retain cursors'
when adding a savepoint unless there is a plan to allow specification
without this sometime in the future. I'm on V5.3 .

Jonathan

.

Relevant Pages