Re: Effective deadlock handling

From: Bricklen <Xbricklen_at_yahoo.comX>
Date: Sun, 04 Jan 2004 02:37:37 GMT
Message-ID: <R%KJb.932500$pl3.437541@pd7tw3no>

Daniel Morgan wrote:
<snip>
> As I understand it the wait with a SELECT FOR UPDATE is not a deadlock
> but rather an intentional wait. With a slight change in syntax ... SKIP
> ... that doesn't happen.
>

http://dictionary.reference.com/search?q=deadlock

A standstill resulting from the opposition of two unrelenting forces or factions.
Sports. A tied score.
Computer Science. A failure or inability to proceed due to two programs or devices both requiring a response from the other before completing an operation.

> To my way of thinking this is not a deadlock as it generates no error > condition.

Who said it had to generate an error? Received on Sat Jan 03 2004 - 20:37:37 CST