Subject | Re: lock conflict on no wait transaction |
---|---|
Author | alex_vnru |
Post date | 2002-02-20T11:40:53Z |
--- In ib-support@y..., "luisfelipepetrycabral" <lcabral@a...> wrote:
not "column". So, second transaction see that master record was
changed and, don't knowing (because first transaction is'nt commited
yet) about does changes affected referenced columns or not,
pessimistically raises lock conflict.
Best regards, Alexander V.Nevsky.
> What I don't really understand is that App-A updates theLuis, it is as IB/FB designed. Locks are watched on "record" level,
> MASTER_DUMMY field, not the MASTER_KEY that is referenced by the
> foreign key of DETAIL table.
not "column". So, second transaction see that master record was
changed and, don't knowing (because first transaction is'nt commited
yet) about does changes affected referenced columns or not,
pessimistically raises lock conflict.
Best regards, Alexander V.Nevsky.