On 11/25/05 9:12 PM, "Stephan Szabo" <[EMAIL PROTECTED]> wrote:
> The latter, the row locks before were single owner and were such that a
> second lock request for the same row would wait for the first to be
> released. Now effectively you have two levels of locks at the row level,
> the weaker of
On Fri, 25 Nov 2005, Wes wrote:
> On 11/25/05 2:40 AM, "Stephan Szabo" <[EMAIL PROTECTED]> wrote:
>
> > 8.1 should be using the new shared row locks for doing the checks. This
> > should fix the case mentioned.
>
> Hmm. I'm looking in the "What's new" for 8.1 and see that now. I could
> have sw
On 11/25/05 2:40 AM, "Stephan Szabo" <[EMAIL PROTECTED]> wrote:
> 8.1 should be using the new shared row locks for doing the checks. This
> should fix the case mentioned.
Hmm. I'm looking in the "What's new" for 8.1 and see that now. I could
have sworn it wasn't there the last time I looked.
On Fri, 25 Nov 2005, Wes wrote:
> I haven't seen anything to indicate that 8.x improves foreign key
> refererence locking and fixes the foreign key 'deadlock detected' issue.
> Has that been addressed in 8.1?
8.1 should be using the new shared row locks for doing the checks. This
should fix the
I haven't seen anything to indicate that 8.x improves foreign key
refererence locking and fixes the foreign key 'deadlock detected' issue.
Has that been addressed in 8.1?
I sort my records before loading, but am still getting 'deadlock detected'
(still running 7.3.4).
I have
B references C
B
