Subject | Re: [ib-support] Deadlock and wait |
---|---|
Author | Robert F. Tulloch |
Post date | 2001-07-27T00:44:44Z |
HI:
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???
> If transaction A attempts to update a row that transaction B has alreadyDon't understand this. Why is it an deadlock if B has committed? If deadlock in this
> 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.
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???