Subject Re: Commit Client Transaction - Monitoring Tables
Author Adam
> Yes, an insert can cause a lock conflict if the target of a foreign
> key constraint is updated. In fact Firebird has to be even more
> pessimistic here because while it can see whether the target has been
> updated, it currently has no way of knowing whether it was only the
> other fields that have changed.

Edit:

Also, primary key (or indeed all unique constraints) are potential
causes of conflicts.