RE: Complex Integrity Checking

From: Jamadagni, Rajendra <Rajendra.Jamadagni_at_espn.com>
Date: Wed, 05 Jun 2002 05:23:36 -0800
Message-ID: <F001.00474DC0.20020605052336@fatcity.com>

no matter what you do, if you access table A inside a trigger on table A, oracle will give you mutating table error. What you could (and I really mean you have to consider your business logic here) is go ahead and insert the rows with a temp flag. As soon as you commit, fire up a procedure that will do the scan on the table and delete appropriate rows which have the temp status.

BTW how big is this table? What is the frequency of inserts and updates?

Raj

---

Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
Any opinion expressed here is personal and doesn't reflect that of ESPN Inc.

QOTD: Any clod can have facts, but having an opinion is an art!

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Jamadagni, Rajendra
  INET: Rajendra.Jamadagni_at_espn.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).



text/plain attachment: InterScan_Disclaimer.txt

Received on Wed Jun 05 2002 - 08:23:36 CDT