Hello José,
The conversion is done if there are more row locks the internal data structures
can hold are requested. That size is defined by MAXLOCKS.
You can only *avoid* them, by increasing the MAXLOCKS parameter to a reasonable
value. Lock escalations are part of the normal behaviour of MaxDB
Hi Jose,
>From my test on MaxDB 7.5.0.8, your desired behavior can be "partially" achieved by
>using isolation level 15.
I mean "partial" because when T1 attempts DML (Insert, Update, Delete) later - to the
"locked" row or other rows, to the same table or other tables - there is an automatic
l
-48-13
Cel: (311) 910-50-59
From: "Hahn, Uwe" <[EMAIL PROTECTED]>
To: 'José Rómulo Elías Contreras' <[EMAIL PROTECTED]>,
[EMAIL PROTECTED]
Subject: RE: Question about locks
Date: Mon, 22 Mar 2004 08:57:05 +0100
Yes, T2 can update the row R1.
If you want that
Yes, T2 can update the row R1.
If you want that T2 can only read committed rows
then you have to use isolation level 1.
This will synchronize T1 and T2 with each other.
Kind regards,
Uwe
>-Original Message-
>From: José Rómulo Elías Contreras [mailto:[EMAIL PROTECTED]
>Sent: Saturday, Mar
