Re: Locking outside COMMIT WORK

Bryan Tonnet wrote: > > In <3251409F.6A4E@explorer.csc.com> "Chao Y. Din" <cdin@explorer.csc.com> writes: > > I dont think will help me, as the problem I have is with holding the locks, > not holding the cursor open. My rows are always selected via the temp > table (indirectly). The cursor option is a go-er if I have to reopen (and > reread) the rows after each commit work in order to pick up the locks again. > > Bryan Tonnet > batonnet@zeta.org.au I believe hoding a cursor is equivalent to holding a lock (I may be wrong on this). What I was thinking was to have some structure like foreach ... on hold select ... if all rows have been read then foreach ... ... rollback and/or commit end foreach end if end foreach In this case, you will not issue the rollback/commit command for every MASTER cursor. Sorry, it is just a *theory*. I am not sure whether it will work or not. Chao