In the example, the row already exists before either TX. Thread B reads the row as it
was before either TX started, with val = 1.
Hope this makes things clear.
On Sat, 30 Jun 2001 11:46:31 +0530, kvrprasad <[EMAIL PROTECTED]> wrote:
>Lawrence , you wrote:
>>A row exists with some field value of 1. Two different threads associated
>>with different TXs want to increment this value by one. Thread A reads
>>the row, see val=1. Thread A updates the row to val = 2. No commit of
>>the TX yet.
>>
>>Then Thread B reads the row, sees val = 1 (default isolation used,
>>read-committed). Then Thread B tries to update the row to val = 2, but
>>hangs, because there is an uncommitted update on that row in another TX.
>can you please tell me how can Thread B read the row with isolation level of
>read-committed , when the row is in the scope of the transaction started
>by Thread A and ThreadA has not yet committed the TX.
>thank you,
>regards.
>
> ==========================================================================
>To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
>of the message "signoff EJB-INTEREST". For general help, send email to
>[EMAIL PROTECTED] and include in the body of the message "help".
>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
