Subject Re: [firebird-support] Lock conflicts
Author Martijn Tonies
Hi Tim,

> I am getting the following error :
>
> "lock conflict on no wait transaction"
>
> What causes it? How can I resolve it?

It's caused by a deadlock:

1 transaction having changed a record but not committed yet,
and another transaction attempting to change this record as well.


With regards,

Martijn Tonies
Database Workbench - the developer tool for InterBase & Firebird
Upscene Productions
http://www.upscene.com