Re: Trigger Code

>
> i supplied an explicit example in my 3/21 post
>
> why are you assuming there's a problem with oracle update triggers?
>
> and why would you expect an update trigger that does further updates to
not
> cause additional triggers to fire? if they didn't, you'd have to recode
the
> same logic (or explicitly invoke it) from multiple places?
>
> unfortunately, you've gotten a lot of unnecessary flack in response to
your
> original question, along with a few good suggestions on interviewing
DBAs --
> but sticking strictly to the technical issues, i think you've reached a
> faulty conclusion.
>
> ;-{ mc

Well, I tried to test that trigger and I keep getting an error message that the trigger is mutating.
I tried to fire on "Before update" and "After Update" specifying that the trigger only fires on update to quantity field. It still sees the trigger as a recursive operation even though the update is to
another field other than the field that fired the trigger. It seems like you
can not start another update in the middle of an update even if you specify "Before Update". Someone told me that this type of trigger would be a good question and now I now why.
Feel free to test it yourself.

Thanks for you responces to my posts.

>
Received on Tue Mar 23 2004 - 11:55:41 CST