Re: oracle concurrent
Date: 1996/01/31
Message-ID: <0oTqEFAus7DxEwQB_at_tomcooke.demon.co.uk>#1/1
In article <310FAE65.1232_at_us.oracle.com>, "Robert C. Nix"
<rnix_at_us.oracle.com> writes
>> lee (lee_at_cnct.com) wrote:
>> problem:
>> how to avoid two user SELECT same data from database,
>> and one's UPDATE + COMMIT overwrite another one's UPDATE +
>> COMMIT ?
>> we don't want lock the row after SELECT, but want lock
>> the row after UPDATE, and before COMMIT, how to do
>> this ?
>> Thank you.
>
>one option is to add a date_modified column to the table.
> stuff deleted
Sounds like bad business process/application design - which user has the "correct" data i.e. accurately represents some aspect of the real world, which is what databases are for, no?
-- Tom CookeReceived on Wed Jan 31 1996 - 00:00:00 CET