Dirk Zoettl wrote: > I have a problem concerning transaction locking using multiple > concurrent transactions. In one transaction a new row is inserted > and before the commit a query in another transaction is executed. > For the second transaction I expect to see the state without the > new row, but in SAP DB I get a lock exception. It seems, that an > insert will give a table lock. > > Changing the transaction isolation level to one of REPEATABLE_READ > or SERIALIZABLE will throw the lock exception too. > > Using READ_UNCOMMITTED will not throw an exception, but does not > give the desired result. > > How can the given problem be solved ? >
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/738ef13f4a11d3a98200a0c9449261/frameset.htm HTH. Kind regards, Holger SAP Labs Berlin _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
