Subject Re: Lock conflict on no wait transaction
Author Svein Erling Tysvær
--- In, "pungsven" wrote:
> My question is what went wrong and how can I fix it?
> I think it maybe has something to do with when one user edits a
> record while another is reading it.

This should not cause any problems in Firebird, the reader should see
the old version and the writer be allowed to change the record.
Rather, the problem is likely to be that the record has been changed
within one transaction that is not (yet) visible to another
transaction. This other transaction will then be denied updating the
record (or at least denied committing the transaction). So it is a
case of two writers, not one writer and one reader (though they may be
attemping to update different fields).