Hi, 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? 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? My application opens a database connection with AutoCommit Off and IsolationLevel UnCommitted via ODBC. BTW, it seems that there is a difference between the isolation levels of ODBC and SAP DB. ODBC talks about Commited and UnCommited and SAP DB talks about levels 0, 1, 2 and so on. How do they match? Any suggestions for solving the locking problem? Best regards, Ralf. -- ## Ralf Schneider ## B-connected Linux Solutions GmbH - Linux f�r den Mittelstand ## Dennis-Gabor-Str. 2, 14469 Potsdam ## www.b-connected.de _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
