Re: Multiple "before insert" triggers on a table?

In article <3ea56f28$1_at_rutgers.edu>, T_at_T wrote:

>I'm wondering about the real-world (non theoretical!) impact of multiple
>"before" triggers on a table. All I can find on the 'net is that multiple
>before/after update/insert triggers aren't a good idea, since you can't
>specify what order they execute in. But what if order doesn't matter?

Wouldn't it be better (and easier to maintain) if you put everything into one trigger instead of several little ones? That would put them all in one place and allow you control the order as well.

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