Whoops, the defective configuration of the mailinglist caused me to oreply directly to Elke (thanks for the quick answer btw)
-------- Original Message -------- Subject: Re: Inserting without setting locks Date: Thu, 31 Jan 2002 11:54:31 +0100 From: Flemming Frandsen <[EMAIL PROTECTED]> To: "Zabach, Elke" <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> "Zabach, Elke" wrote: > > I'd like to insert into a table, without *ever* setting a single lock. > It is NOT possible to avoid locking of a dml > (insert/update/delete)-call. That's ok as long as I can avoid checking for the locks. > Let those other processes use isolation level 0 or this special select > (see reference manual --> ...--> lock_option > > http://www.sapdb.org/htmhelp/e2/55683ab81fd846e10000000a11402f/frameset.htm Hmm, the page doesn't work on Konqueror, boo, hiss. Nevermind I have pdf reader. Page 197: <lock_option> ::= WITH LOCK [(NOWAIT)] [EXCLUSIVE] [ISOLATION LEVEL <unsigned_integer>] WITH LOCK [(NOWAIT)] OPTIMISTIC [ISOLATION LEVEL <unsigned_integer>] So if I tack: WITH LOCK ISOLATION LEVEL 0 or WITH LOCK OPTIMISTIC ISOLATION LEVEL 0 Onto my selects then they will not check for or set locks? * Am I right in assuming that level 0 means that the select can never cause a deadlock? * Am I right in assuming that the OPTIMISTIC keyword doesn't mean anything when level 0 is used? * What locks are set when I execute: select sum(somecol) from sometable where mumble=42 in isolation level 1, 2 and 3? -- Regards Flemming Frandsen aka. Dion/Swamp http://dion.swamp.dk _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
