| Subject | Triggers best practice |
|---|---|
| Author | firebirdsql |
| Post date | 2011-06-13T13:54:01Z |
I have a couple of tables that have tallys and several triggers that maintain these tallys.
Some of the updates can trigger the same trigger multiple times (since firebird fires a trigger per row). Is this considered best practice or would a stored procedure be better (don't really like to use stored procedures since it adds an extra level of maintenance)?
Some of the updates can trigger the same trigger multiple times (since firebird fires a trigger per row). Is this considered best practice or would a stored procedure be better (don't really like to use stored procedures since it adds an extra level of maintenance)?