Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Re: ** table triggers
A hearty second to the "rethink the design" advice. Always good advice when
a problem starts getting too difficult...
...but, I think you can resolve this using package variables. Assuming these are both row-level triggers, have each set the same boolean package variable to TRUE if the value is FALSE and then reset it to FALSE upon completion of the trigger. If the value of the package variable is already TRUE, then don't do anything.
on 7/30/03 11:09 AM, Mladen Gogala at mgogala_at_adelphia.net wrote:
> You can't. An update statement is what fires the trigger. Trigger cannot > see where does the statement come from. May be you should rethink the overall > design of the application? > > On 2003.07.30 13:59, A Joshi wrote:
-- Please see the official ORACLE-L FAQ: http://www.orafaq.net -- Author: Tim Gorman INET: tim_at_sagelogix.com Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services --------------------------------------------------------------------- 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).Received on Mon Aug 04 2003 - 13:04:29 CDT
![]() |
![]() |