Subject | Re: [ib-support] 81 triggers for 27 tables - overkill? |
---|---|
Author | Ann W. Harrison |
Post date | 2002-05-02T19:17:59Z |
At 03:45 PM 5/2/2002 -0300, Lista de Discução Interbase wrote:
table is referenced.
trigger to be defined to fire both before (or after) insert and
update. Probably also something that would fire on update and
delete.
Regards,
Ann
www.ibphoenix.com
We have answers.
>I prefer one trigger for each process (the first approach), I think thisThat's why InterBase had many triggers per operation.
>way you have a more managable code
>But, I do not know if having 3 trigger instead of one could cause aNo - the triggers are all compiled together the first time the
>performance decrease. I don't think so.
table is referenced.
>> A lot of these are duplicated triggers, that is they need to fireSomething we've talked about doing in the future is allowing one
>> both for insert and update.
trigger to be defined to fire both before (or after) insert and
update. Probably also something that would fire on update and
delete.
Regards,
Ann
www.ibphoenix.com
We have answers.