Re: Triggers?

In article <E517MA.F0C@nonexistent.com>, Jacob Salomon <jake@apparel.net> writes >Joseph Kormann wrote: >> >>Howdy. At work we're starting to play / test triggers on our SE4.13UC1 >(HPUX). >Is there any way that you can recommend that's pretty >>straightforward to reduce / eliminate trigger-cascade? Basically I'm >>fearing an endless loop of triggers if we're not careful. >> >> Thanks, >> Joseph > >Joseph, > >You must be a propaganda shill for Informix. ;-)) > >There is a restriction on triggers that absolutely prevents the >recursion that would cause an endless loop. You cannot reference the >triggering column in the the trigger code or any stored procedure it >invokes. The reason for this restriction is exactly to prevent >recursion. > >Most of us out here wish this restriction would go away. This is a >popular feature reqest, judging by the postings I have seen. Why can't they make the limit 61 as with cascading deletes? Also what happens it update a row and you fire a trigger(Trigger 1). That trigger (Trigger1) changed the new value being put into the table (value1) to value2. This also and also updates another table which fires another trigger (trigger2) which does another update of the same row and column (with value 3). This fires trigger 1 again which changes value3 to value and stops. Which value does the row and column get in the end. value2,value3 or value4? PS I'm trying not to write tigger but I'm a bear of very little brain so forgive finger errors. -- David Williams