Updating clause used in instead of trigger example

Posted by / 12-Jul-2020 10:50

Row-level DML triggers are not allowed to query or perform any DML on the table that fired them.If they attempt to do so a mutating table exception is raised.SQL DELETE FROM trigger_test; BEFORE STATEMENT - DELETE BEFORE EACH ROW - DELETE (old.id=2) AFTER EACH ROW - DELETE (old.id=2) BEFORE EACH ROW - DELETE (old.id=1) AFTER EACH ROW - DELETE (old.id=1) AFTER STATEMENT - DELETE 2 rows deleted.SQL From this we can see there is a single statement level before and after timing point, regardless of how many rows the individual statement touches, as well as a row level timing point for each row touched by the statement.If an exception is raised by the DML itself or by the trigger code, no more timing points are triggered.This means the after statement trigger is not fired, which can be a problem if you are using the after statement timing point to do some important processing.

: updating clause used in instead of trigger example-73updating clause used in instead of trigger example-13updating clause used in instead of trigger example-51

The workaround for this is to use variables defined in packages to store information that must be in scope for all timing points.

One thought on “updating clause used in instead of trigger example”

  1. In 2008, Karina Schaapman, a former prostitute and former member of the Amsterdam city council, produced a report about the Amsterdam sex trade.