View Revisions: Issue #6486
| Summary | 0006486: Wildcard trigger definitions do not remove existing triggers when adding a NOT table name to wild carded definition | ||
|---|---|---|---|
| Revision | 2024-06-10 18:38 by pmarzullo | ||
| Description | When you have a wild card trigger definition, and the triggers are already built on the tables that the trigger definition applies to, if you add a NOT constraint to the trigger definition list, the triggers on the table that has a NOT constraint does not get the triggers removed. For example, if you have "*" for the source table name, and you change it to: *,!Company the triggers that exist on the Company table are not removed. This issue ends up causing tables to have multiple sets of Insert, Update, and Delete triggers created on the table when another trigger defines triggers for the Company table. |
||
| Revision | 2024-06-10 17:50 by pmarzullo | ||
| Description | When you have a wild card trigger definition, and the triggers are already built on the tables that the trigger definition applies to, if you add a NOT constraint to the trigger definition list, the triggers on the table that has a NOT constraint does not get the triggers removed. For example, if you have "*" for the source table name, and you change it to: *,!Company the triggers that exist on the Company table are not removed. This issue ends up causing tables to have multiple sets of Insert, Update, and Delete triggers created on the table. |
||