Subject | Re: interleaved transactions and deadlocks |
---|---|
Author | Ludovic Orban |
Post date | 2006-11-17T18:47:57Z |
Hi,
--- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"
descriptive I'd be glad.
Thanks,
Ludovic
--- In Firebird-Java@yahoogroups.com, "Roman Rokytskyy"
> I have forwarded your email to engine developers, my ideas are below.Thanks.
> In general FB throws two different types of exceptions - one fordeadlock
> and one for lock timeout. And in different places of the enginedifferent
> types of locks are requested. I have a list with places of what locktype is
> requested where (and corresponding error codes), but I have toconfirm that
> from _my_ POV these are not consistent.applications that
>
> I guess that we have to create different test cases and then start the
> discussion in the FB-Architect list. On the other hand, I really-really
> doubt that things will be changed, since there's so many
> might (and do) rely on this feature, that changing it would break them.I don't want to change anything, I would just like to understand.
>
> But anyway, the test cases (or just an explanation) would be useful, at
> least for documentation purposes.
> PS. BTW, do you know that starting FB 2.0 the lock timeout can becontrolled
> via TPB. That means that in XA-mode we can reduce the differences toone
> case - "immediate" deadlock notification.Sorry, I don't understand that. If you could be a little more
descriptive I'd be glad.
Thanks,
Ludovic