Subject | Re: [ib-support] Deadlock and wait |
---|---|
Author | Woody |
Post date | 2001-07-26T16:55:55Z |
From: "Robert F. Tulloch" <tultalk@...>
Sent: Thursday, July 26, 2001 11:47 AM
but Delphi that handles that. Even so, it stills leaves a transaction open.
The only way to fully end a transaction is to close all datasets.
was in a transaction. If that's not the case, then it's my mistake.
Regardless, as long as A doesn't actually change anything directly on the
server and his changes are only client side, there is no problem until he
actually posts the changes, right?
Woody
Sent: Thursday, July 26, 2001 11:47 AM
>That's what I do most times but left it out because it's not Interbase
> CommitRetaining()
>
but Delphi that handles that. Even so, it stills leaves a transaction open.
The only way to fully end a transaction is to close all datasets.
>I assumed that B would get a deadlock because the record changed while he
> Why would B get a deadlock if A has already committed?
>
was in a transaction. If that's not the case, then it's my mistake.
Regardless, as long as A doesn't actually change anything directly on the
server and his changes are only client side, there is no problem until he
actually posts the changes, right?
Woody