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!
*********************************************************************This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank you.*********************************************************************2
