Re: SELECT FOR UPDATE problem

In article <881pv7$ul7$1@duke.telepac.pt>, "P.S." <psilva69 @ hotmail.com> wrote: > But if I use a repeatable read isolation level every select I execute (even > those that aren't meant to be for update) will lock the selected rows to > every user (even those trying to make a simple report to printer. Isn't it > so? BTW we are using the COMMITED READ mode. > > Thanks for your help. > P.Silva > Critical Software > PORTUGAL > > <yap123@my-deja.com> wrote in message news:87vor1$8s6$1@nnrp1.deja.com... > > You have to use an isolation level (repeatable read) > > > > Hi, version 7.31 and above and 9.20 and above provide new isolation levels: - set isolation to dirty read retain update locks - set isolation to committed read retain update locks - set isolation to cusor stabilitiy retain update locks These new isolation levels are intended to retain locks set by update cursors until end of transaction. Documentation should be found in the release notes (if it's not yet in the manuals). Hope this helps, Heiko Sent via Deja.com http://www.deja.com/ Before you buy.

Wow, thanks! I think I'll try these (if our version is above 7.31 wich I'll check) in conjunction with Delphi to see the results. The process of upgrading Informix is a very complicated issue around here (the whole mill depends on it so the upgrade is only made a few months or even years after the release is available and throughly tested - by others :)) ) so I guess we're condemned to the "dummy update" technique if our release is prior 7.31. Thanks - again! Paulo Silva Critical Software PORTUGAL <giesselm@my-deja.com> wrote in message news:8823fg$vr7$1@nnrp1.deja.com... > In article <881pv7$ul7$1@duke.telepac.pt>, > version 7.31 and above and 9.20 and above provide > new isolation levels: > - set isolation to dirty read retain update locks > - set isolation to committed read retain update > locks > - set isolation to cusor stabilitiy retain update > locks >