Subject | Re: [firebird-support] Lock conflicts |
---|---|
Author | Martijn Tonies |
Post date | 2003-06-17T14:13:54Z |
Hi Tim,
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
> I am getting the following error :It's caused by a deadlock:
>
> "lock conflict on no wait transaction"
>
> What causes it? How can I resolve it?
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