Re: Record Locking

Suresh Kumar Bathini (bathini@netcom.com) wrote: : Hi There: : I have two clients in their transactions as below. : Client1----> : begin work : fetch a record R1 : : ..... : update R1 : commit work : Client2-----> : begin work : fetch a record R1 : update R1 : commit Work : Both the clients fetched the same record but client2 updated R1 before : client1 did, so this resulted in client1's R1 to be an old copy. Is : there a way I could lock a record to read in a transaction? Or is this : kind of problem accepatable in Relational world as R1 is a copy and : doesn't guarentee its state in d/b? : Thanks in advance for ur answers. : suresh Look to your isolation levels. Setting a high (restrictive) enough isolation level will allow OnLine to handle this problems. Looks like you're probably using a dirty read isolation level. You probably need cursor stability isolation. Joe -- =========================================================================== jlumbley@netcom.com (Joe Lumbley) BancTec Service Corportation 214-450-9894 Dallas, Texas Watch for my _INFORMIX DBA SURVIVAL GUIDE_ in Fall '94 from Prentice Hall! ===========================================================================