Oracle if updating column

')'; END CASE; END trigger_test_ar_trg; / -- AFTER STATEMENT CREATE OR REPLACE TRIGGER trigger_test_as_trg AFTER INSERT OR UPDATE OR DELETE ON trigger_test BEGIN trigger_test_api.g_tab.extend; CASE WHEN INSERTING THEN trigger_test_api.g_tab(trigger_test_api.g_tab.last) := 'AFTER STATEMENT - INSERT'; WHEN UPDATING THEN trigger_test_api.g_tab(trigger_test_api.g_tab.last) := 'AFTER STATEMENT - UPDATE'; WHEN DELETING THEN trigger_test_api.g_tab(trigger_test_api.g_tab.last) := 'AFTER STATEMENT - DELETE'; END CASE; FOR i IN trigger_test_api.g_tab.first ..Row-level DML triggers are not allowed to query or perform any DML on the table that fired them.

oracle if updating column-85oracle if updating column-10

CASE WHEN INSERTING THEN -- Include any code specific for when the trigger is fired from an INSERT. WHEN UPDATING THEN -- Include any code specific for when the trigger is fired from an UPDATE. WHEN DELETING THEN -- Include any code specific for when the trigger is fired from a DELETE. DML triggers have four basic timing points for a single table. With the exception of Compound Triggers, the triggers for the individual timing points are self contained and can't automatically share state or variable information.This can become a little awkward when you have a parent-child relationship and a trigger on the parent table needs to execute some DML on the child table.If the child table has a foreign key (FK) back to the parent table, any DML on the child table will cause a recursive SQL statement to check the constraint.5 LOOP l_tt_tab.extend; l_tt_tab(l_tt_tab.last):= i; l_tt_tab(l_tt_tab.last).description := 'Description for '