Very Computer

Given the situation where you BEGIN WORK and shortly thereafter you
want to end the transaction *but nothing has been altered*, WRT efficiency
is it better to COMMIT or ROLLBACK?

e.g.

FUNCTION xyz()
        BEGIN WORK
        IF (NOT LockSomeRecord())       -- Failed
                ROLLBACK WORK           -- Better to COMMIT?
                RETURN
        END IF

        ...
        COMMIT WORK
END FUNCTION

where LockSomeRecord declares a cursor for update, and fetch's the row

-SRK

--

James Cook University
Townsville                      Tel: +61 77 814992
Qld 4811 Australia              FAX: +61 77 814029

If you are sure nothing's been done that you don't want to keep, then COMMIT.  
Commit is the least amount of work.

--

  Disclaimer: Sender under influence of 1,3,7-trimethylxanthine

My understanding is that Informix always assumes the best, so that
COMMIT WORK just releases any locks, while a ROLLBACK WORK needs to
trundle back thru the transaction and "undo" everything.

------------------------------------------------

 R&D Dude, Quanta Systems, Auckland, New Zealand
 ph. +64 9 377-4473 (work). +64 9 276-5546 (home)
-------------------------------------------------