I'm about to add a trigger to format phone numbers in several tables. I already have after insert & after update triggers on some tables which are called when any changes are made for auditlog purposes.

The question is wether it would be better to place the code in the existing trigger or have a series of new triggers that only respond to changes to the specific fields involved?

Roy Lambert

ps Tim any news on being able to fully specify the location of external modules?

A quick experiment provided part of the answer I need a before update trigger, so what's your views. One trigger to handle many columns and sorting it out inside or one trigger per column?

Roy Lambert

Roy,

<< ps Tim any news on being able to fully specify the location of external
modules? >>

Not yet, still on the list.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy,

<< The question is wether it would be better to place the code in the
existing trigger or have a series of new triggers that only respond to
changes to the specific fields involved? >>

It's strictly up to you.  There's no difference as far as EDB is concerned.

--
Tim Young
Elevate Software
www.elevatesoft.com

Roy,

<< A quick experiment provided part of the answer I need a before update
trigger, so what's your views. One trigger to handle many columns and
sorting it out inside or one trigger per column? >>

Again, it doesn't really matter that much.  The only difference is letting
EDB do the column matching, vs. you trying to figure out which columns have
changed.  EDB already tracks this information (column modifications), so it
can determine it very quickly.

--
Tim Young
Elevate Software
www.elevatesoft.com