Dimitry Sibiryakov wrote:

>On 15 Dec 2003 at 11:17, James wrote:
>
>
>
>>I just want to know what are the situations wherein I have to write more
>>than one trigger for a certain event. Base on my experience, from what I
>>have done so far I think I can put it in only one trigger. Is there any
>>situtation where it really requires more than one trigger for a certain
>>event? or it is just for easy developing, reading, and debugging triggers?
>>
>>
>
> The main proclaimed advantage of multiple triggers is an ability to
>temporary disable some actions leaving others working. For example,
>you can stop logging during bulk import but keep autoincrement
>working.
> Altering one big trigger (when you need to add or drop
>functionality) is an expensive operations and prefers to be performed
>when no-one is connected. Adding or dropping a whole trigger is
>easier, IMHO.
>
> SY, Dimitry Sibiryakov.
>
>
>
>

Thanks to all of you! I learn a lot from all of you. In short having
multiple trigger in a certain event really help us simplified things for us.

Cheers

James