And deleting the trigger condition identify the triggering event
ALTER TRIGGER trigger_name { ENABLE | DISABLE };
ALTER TABLE table_name { ENABLE | DISABLE } ALL TRIGGERS;
The DML events include INSERT, UPDATE, and DELETE statements on a table. An INSTEAD OF trigger is associated with a view and fires in lieu of DML to that view. Triggers on these events can be statement-level triggers (table only) or row-level triggers, and can fire BEFORE or AFTER the triggering event. BEFORE triggers can modify the data in affected rows, but perform an additional logical read. AFTER triggers do not perform this additional logical read and therefore perform slightly better, but are not able to change the :new values.
Triggers | | | 125 |
---|
AFTER triggers are thus better suited for data-validation func‐tionality. Triggers cannot be created on SYS-owned objects. The order in which these triggers fire, if present, is as follows:
5. AFTER statement-level trigger
Compound DML Triggers
126 | | |
---|