Dirk Zoettl wrote: > > Becker, Holger wrote: > > > > With SAP DB version 7.3.0.21 and 7.4.3 the new lock option > "ignore" is available > > which seems to be what you are looking for. > > > > Here a snippet from the 7.4 reference manual: > > > > "If (IGNORE) is specified, the system does not wait for a > locked row to be released > > by another transaction. Instead, it ignores this row if a > lock collision occurs. > > If there is no collision, the requested lock is set. > > (IGNORE) can only be specified in isolation level 1." > > > > The whole story about lock option you'll find here > > > http://www.sapdb.org/7.4/htmhelp/ac/738ef13f4a11d3a98200a0c944 > 9261/frameset.htm > > > > I removed my 7.3.0.20 version and installed 7.3.0.29 . > > Trying the lock option IGNORE will give an exception. Is it usable > on 7.4 only ? > > getDatabaseProductVersion : "Kernel 7.3.0 Build > 029-000-087-809" > getTransactionIsolation : TRANSACTION_READ_COMMITTED > > com.sap.dbtech.jdbc.exceptions.DatabaseException: SAP > DBTech SQL: [-3008] (at 31) Invalid keyword or missing delimiter > > Sincerely, > Dirk Z�ttl
Mhm, if we are talking about internal mode and the syntax ... WITH LOCK (IGNORE) which results in the error given above, then please provide a vtrace to see how the statement exactly looks like which is send to the SQL-parser. please see : http://sapdb.2scale.net/moin.cgi/VTrace Elke SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
