Subject Re: [ib-support] Deadlock and wait
Author Woody
From: "Robert F. Tulloch" <tultalk@...>
Sent: Thursday, July 26, 2001 11:47 AM
> CommitRetaining()

That's what I do most times but left it out because it's not Interbase
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.

> Why would B get a deadlock if A has already committed?

I assumed that B would get a deadlock because the record changed while he
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?