Subject | Re: [firebird-support] Deadlock when 2 session update the same 01 row |
---|---|
Author | Michael Ludwig |
Post date | 2012-11-28T22:43:25Z |
Ann Harrison schrieb am 28.11.2012 um 16:07 (-0500):
Fortunately, while I agree the term »deadlock« is confusing,
the full error message is rather clear and descriptive:
Statement failed, SQLSTATE = 40001
deadlock
-update conflicts with concurrent update
-concurrent transaction number is 488
Michael
> On Wed, Nov 28, 2012 at 9:42 AM, André KnappsteinI really like those history lessons, thanks, Ann! :)
> <Knappstein@...> wrote:
>
> > … the default is "NoWait". This makes my misunderstanding
> > of the term "deadlock" complete, because in NoWait I usually get
> > an exception right off, which is all but a deadlock in the way I
> > used to understand it.
> >
>
> There's a some history and a bit of theory here.
Fortunately, while I agree the term »deadlock« is confusing,
the full error message is rather clear and descriptive:
Statement failed, SQLSTATE = 40001
deadlock
-update conflicts with concurrent update
-concurrent transaction number is 488
Michael