View Revisions: Issue #4050
| Summary | 0004050: Dropping a trigger from the Installed Triggers UI should probably NOT invalidate the trigger_hist but instead log a console evnt | ||
|---|---|---|---|
| Revision | 2019-07-23 15:59 by hanes | ||
| Description | Currently, when dropping a trigger via the Installed Trigger UIs, the triggers are dropped, and the table's trigger_hist entry is inactivated. This causes confusion if doing a Load, for example, in that the table will potentially show in the list of tables but no load event for the table will appear in the batches (due to that table not having an active trigger_hist row). In addition, a console event should be logged for recordkeeping, showing that the user 'manually' dropped the triggers. |
||
| Revision | 2019-07-17 17:20 by hanes | ||
| Description | Currentyl, when dropping a trigger via the Installed Trigger UIs, the triggers are dropped, and the table's trigger_hist entry is inactivated. This causes confusion if doing a Load, for example, in that the table will potentially show in the list of tables but no load event for the table will appear in the batches (due to that table not having an active trigger_hist row). In addition, a console event should be logged for recordkeeping, showing that the user 'manually' dropped the triggers. |
||
| Revision | 2019-07-17 17:19 by hanes | ||
| Description | Currentyl, when dropping a trigger via the Installed Trigger UIs, the triggers are dropped, and the table's trigger_hist entry is inactivated. This causes confusion if doing a Load, for example, in that the table will potentially show in the list of tables but no load event for the table will appear in the batches (due to that table not having an active trigger_hist row) | ||