Hi, I found the following in the Oracle Application Developer�s Guide: >>Do not create recursive triggers. For example, creating an AFTER UPDATE >>statement trigger on the Emp_tab table that itself issues an UPDATE >>statement on Emp_tab, causes the trigger to fire recursively until it has >>run out of memory. So , there is no more "Table is mutating..." errors ?? How does oracle guarantees the integrity on the table ?? TIA, Antonio Belloni -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: [EMAIL PROTECTED] 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: [EMAIL PROTECTED] (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).
