Because A see an old version of record updated by B. This avoid lost of
integrity. I think! :o)

Dufloth.

----- Original Message -----
From: "Robert F. Tulloch" <tultalk@...>
To: <ib-support@yahoogroups.com>
Sent: Thursday, July 26, 2001 9:44 PM
Subject: Re: [ib-support] Deadlock and wait


> HI:
>
> > If transaction A attempts to update a row that transaction B has already
> > changed, the WAIT option causes A to wait for B to end before reporting
> > an error to A. If B rolls back, A succeeds. If B commits, A gets a
> > Deadlock - update conflict error.
>
> Don't understand this. Why is it an deadlock if B has committed? If
deadlock in this
> case is correct then if A closes then reopens A can update, right? So why
can A update
> 1 sec after B commits or .001 sec after B commits???
>
> Yahoo! Groups Sponsor
> ADVERTISEMENT
>
>
>
>
> To unsubscribe from this group, send an email to:
> ib-support-unsubscribe@egroups.com
>
>
>
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
>
>