🚀 go-pugleaf

A deadlock is when a statement (i.e. UPDATE) locks for example row 1 and
then tries to update row 2.
In the mean time another user has locked and edited row 2 and now tries to
update row 1.

So, row 1 is locked by user 1 and row 2 is locked by user 2 who are now both
waiting for the other user to release the lock.

The situation in your last sentence will (in my option) not generate a error
because the second statement will wait till the records are release from the
lock and either 1) try to delete or update a row that already is deleted (=
no problem) or 2) update or delete a row that is updated which will not
generate a database error but you should write your software to prevent
this. (i.e. check how much rows are edited / deleted after the stament and
compare this to what you expect)

Hope this helps,

Greetings,
Thomas

"Edward Diener" <eddielee@tropicsoft.com> wrote in message
news:3dff68ba$1@newsgroups.borland.com...
> What does the IB isc_deadlock error mean ? What is the difference between
it
> and isc_lock_conflict ? If TXA updates or deletes a record and TXB
attempts
> to update or delete that record before TXA has finished, what IB error
> message is received in the exception ?
>
>