Re: Record has been change by another user please re-query ???

From: David J Natelson <dnatelso_at_us.oracle.com>
Date: 1995/12/29
Message-ID: <4c14ho$e4k_at_inet-nntp-gw-1.us.oracle.com>#1/1


chuckh_at_ix.netcom.com (Chuck Hamilton) writes:

>staccuc_at_riq.qc.ca (Sylvain Taccucci) wrote:
>
>>When FORMS detect that a queried record has been change by another
>>user, it tells you so as soon as you tried to modify it, that is when
>>FORMS tried to lock it. Which mecanism FORMS use in order to know
>>that the record has been changed ???
>
>It re-queries the record immediately prior to updating and compares it
>to the originally queries values. Power builder does the same thing.
>You should be able to prevent this by doing the initial select as a
>"FOR UPDATE" select. Nobody else can change it then.

Forms has two ways it to do this:

(1) Immediately lock the record(s) as they are changed (select for update is issued for each rowid to get a row-level lock).

(2) Requery at commit time (deferred locking) and compare values like Powerbuilder does it.

The developer can choose the objects locking strategy via a property sheet attribute setting.

-=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()} David Natelson Oracle Corporation dnatelso_at_us.oracle.com -=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()}>]:=--=:[<{()} Received on Fri Dec 29 1995 - 00:00:00 CET

Original text of this message