Ralf Schneider wrote.
> my application locks a record if it is opened for editing so
> that a second
> user that wants to edit this record at the same time get an
> error message.
> For this, I use an EXCLUSIVE lock.
>
> After reading the reference manual, my understanding was that
> if one record is
> locked exclusively it can be read by another user but not
> modified. Am I right with this?
no, unfortunately not.
For all readers not using ISOLATION LEVEL 0 (dirty read)
the record is blocked to avoid their reading of uncommitted data.
> But when I open a record for editing in my application and
> this record is
> locked, a SELECT from WebSQL on the table with the locked
> record hangs until
> the record is unlocked. Did I understand something wrong?
That is correct if the reader does not use ISO LEVEL 0.
Elke
SAP Labs Berlin
_______________________________________________
sapdb.general mailing list
[EMAIL PROTECTED]
http://listserv.sap.com/mailman/listinfo/sapdb.general
