condition does not return true, it is not necessary to queue an event nor to re-fetch the row at end of statement.
This can result in significant speedups in statements that modify many rows, if the trigger only needs to be fired for a few of the rows.
This option is used for foreign-key constraints and is not recommended for general use.
This can only be specified for constraint triggers.
This is the same as a regular trigger except that the timing of the trigger firing can be adjusted using SET CONSTRAINTS. They can be fired either at the end of the statement causing the triggering event, or at the end of the containing transaction; in the latter case they are said to be deferred.The ability to specify multiple actions for a single trigger using If you see anything in the documentation that is not correct, does not match your experience with the particular feature or requires further clarification, please use this form to report a documentation issue.and repopulate it back with the records from TABLE 1. Would this be a statement trigger that involves a type of collection? If you really do need this duplicate table functionality, then you can certainly use a trigger to create the new/updated record in table 2 when I/U/D's are done on table 1. BEFORE/AFTER INSERT, UPDATE, DELETE ON table_1 FOR EACH ROW BEGIN IF INSERTING INSERT INTO table_2 VALUES (:new.col1, :new.col2, :new.col3..)..so on IF UPDATING UPDATE table_2 SET col1 = :new.col1, col2 = :new.col2....so on WHERE key_column = :old.key_column ; *** another alternative for an UPDATE is that you could DELETE the row that's *** there and then insert a new one as follows DELETE FROM table_2 WHERE key_column = :old.key_column ; INSERT INTO table_2 VALUES (same as when INSERTING) IF DELETING DELETE FROM table_2 WHERE key_column = :old.key_column ; END; By doing it this way, you only deal with one row at a time (in effect).The name cannot be schema-qualified — the trigger inherits the schema of its table.For a constraint trigger, this is also the name to use when modifying the trigger's behavior using The (possibly schema-qualified) name of another table referenced by the constraint.