Re: Dirty Read

If record is locked for update by one session and until change made is commited or rolled back other sessions can read only. If two sessions locked record: first commited changes, then second can commit. Your hold column is redundant - Oracle server has own locking mechanism, and it works. To avoid "dirty" reads by other than updating sessions issue commit statement after update statement.
Good luck!

<goldenge_at_my-deja.com> ÓÏÏÂÝÉÌ/ÓÏÏÂÝÉÌÁ × ÎÏ×ÏÓÔÑÈ ÓÌÅÄÕÀÝÅÅ: news:8ba3is$alc$1_at_nnrp1.deja.com...
> Hi All,
> In Oracle database server , How can I read the uncommitted
> information? Suggest, there are two transaction will update the same
> record at the same time. This will deadlock.
> In our bussiness transaction, the table have a HOLD flag column, when
> user update the record, first he check the HOLD flag , if this is null,
> then he can update this record, and then he update this flag,(this
> update information is uncommitted information, other user can not read
> this from anthor transaction ). If the HOLD flag is not null, then the
> user can get the information that this record is hold by another, so he
> can not update this record. The key problem is another user connect to
> the datatabase from another transaction, he can not read first user
> update the HOLD flag, this flag will be committed with the whole
> transaction .
>
>
> pls give some help!!!!!
>
> Best Regards
>
>
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Received on Wed Mar 22 2000 - 00:00:00 CST