Subject | Re: Lock conflict on no wait transaction |
---|---|
Author | pungsven |
Post date | 2005-07-07T13:06:17Z |
Yes,
Of course you are right.
It is two writers, I realized that after I posted my message.
Right now I am working the steps that David proposed.
BR
svenj
--- In firebird-support@yahoogroups.com, Svein Erling Tysvær
<svein.erling.tysvaer@k...> wrote:
Of course you are right.
It is two writers, I realized that after I posted my message.
Right now I am working the steps that David proposed.
BR
svenj
--- In firebird-support@yahoogroups.com, Svein Erling Tysvær
<svein.erling.tysvaer@k...> wrote:
> --- In firebird-support@yahoogroups.com, "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).
>
> Set