Re: Proving PL/SQL trigger firing sequence

In article <Bm6cb.564595$uu5.92746_at_sccrnsc04>, kennedy-down_with_spammers_at_no_spam.comcast.net wrote:

>"Ubiquitous" <weberm_at_polaris.net> wrote:
>> In article <PEvFa.939$3o3.59705_at_bgtnsc05-news.ops.worldnet.att.net>,
>> sharkmouth_at_worldnet.att.net wrote:
>>
>> >Thanks for the pointers. While I understand that they may unpredictable,
>> >I wondered if running an app with multiple triggers of the same name would
>> >provide consistent results or if each would change every time it was run.
>>
>> I don't think you can use the same name for multiple triggers. I'd
>> make one trigger with all stuff inside.
>
>You can't use the same name for a trigger. Don't be an idiot; the order of
>the same type of trigger on the same table is undefined. You might be able
>to get it to work consistently for some period of time, but later it will
>break. You will be chasing a very difficult problem to detect. Don't do
>it.

Which is why I recomended using a single trigger containing the actions in the sequence desired.

-- 
======================================================================
ISLAM: Winning the hearts and minds of the world, one bomb at a time.