CREATE TRIGGER v16
Name
CREATE TRIGGER
— Define a simple trigger.
Synopsis
Name
CREATE TRIGGER
— Define a compound trigger.
Synopsis
Where private_declaration
is an identifier of a private variable that any procedure or function can access. There can be zero, one, or more private variables. private_declaration
can be any of the following:
- Variable declaration
- Record declaration
- Collection declaration
REF CURSOR
and cursor variable declarationTYPE
definitions for records, collections, andREF CURSOR
cursors- Exception
- Object variable declaration
Where procedure_or_function_definition
:=
Where procedure_definition
:=
Where procedure_body
:=
Where function_definition
:=
Where function_body
:=
Where compound_trigger_definition
:=
Where compound_trigger_event
:=
Where compound_trigger_body
:=
Description
CREATE TRIGGER
defines a new trigger. CREATE OR REPLACE TRIGGER
either creates a trigger or replaces an existing definition.
If you're using the CREATE TRIGGER
keywords to create a new trigger, the name of the new trigger can't match any existing trigger defined on the same table. Triggers are created in the same schema as the table where the triggering event is defined.
If you're updating the definition of an existing trigger, use the CREATE OR REPLACE TRIGGER
keywords.
When you use syntax that's compatible with Oracle to create a trigger, the trigger runs as a SECURITY DEFINER
function.
Parameters
name
The name of the trigger to create.
BEFORE | AFTER
Determines whether the trigger is fired before or after the triggering event.
INSTEAD OF
Modifies an updatable view. The trigger executes to update the underlying tables appropriately. The INSTEAD OF
trigger executes for each row of the view that's updated or modified.
INSERT | UPDATE | DELETE | TRUNCATE
Defines the triggering event.
table
The name of the table or view on which the triggering event occurs.
condition
A Boolean expression that determines if the trigger executes. If condition
evaluates to TRUE
, the trigger fires.
If the simple trigger definition includes the
FOR EACH ROW
keywords, theWHEN
clause can refer to columns of the old or new row values by writingOLD.column_name
orNEW.column_name
.INSERT
triggers can't refer toOLD
, andDELETE
triggers can't refer toNEW
.If the compound trigger definition includes a statement-level trigger having a
WHEN
clause, then the trigger executes without evaluating the expression in theWHEN
clause. Similarly, if a compound trigger definition includes a row-level trigger having aWHEN
clause, then the trigger executes if the expression evaluates toTRUE
.If the trigger includes the
INSTEAD OF
keywords, it can't include aWHEN
clause. AWHEN
clause can't contain subqueries.
REFERENCING { OLD AS old | NEW AS new } ...
REFERENCING
clause to reference old rows and new rows. This clause is restricted in that you can replace old
only with an identifier named old
or any equivalent that's saved in all lowercase. Examples include REFERENCING OLD AS old
, REFERENCING OLD AS OLD
, and REFERENCING OLD AS "old"
. Also, you can replace new
only with an identifier named new
or any equivalent that's saved in all lowercase. Examples include REFERENCING NEW AS new
, REFERENCING NEW AS NEW
, and REFERENCING NEW AS "new"
.
You can specify one or both phrases OLD AS old
and NEW AS new
in the REFERENCING
clause, such as REFERENCING NEW AS New OLD AS Old
.
This clause isn't compatible with Oracle databases in that you can't use identifiers other than old
or new
.
FOR EACH ROW
Determines whether to fire the trigger once for every row affected by the triggering event or just once per SQL statement. If you specify this parameter, the trigger is fired once for every affected row (row-level trigger). Otherwise the trigger is a statement-level trigger.
PRAGMA AUTONOMOUS_TRANSACTION
PRAGMA AUTONOMOUS_TRANSACTION
is the directive that sets the trigger as an autonomous transaction.
declaration
A variable, type, REF CURSOR
, or subprogram declaration. If you include subprogram declarations, declare them after all other variable, type, and REF CURSOR
declarations.
statement
An SPL program statement. A DECLARE - BEGIN - END
block is considered an SPL statement. Thus, the trigger body can contain nested blocks.
exception
An exception condition name, such as NO_DATA_FOUND
and OTHERS
.
Examples
This example shows a statement-level trigger that fires after the triggering statement (insert, update, or delete on table emp
) executes.
This example is a row-level trigger that fires before each row is either inserted, updated, or deleted on table emp
.
This example shows a compound trigger that records a change to the employee salary by defining a compound trigger hr_trigger
on table emp
.
Create a table named emp
:
Create a compound trigger named hr_trigger
. The trigger uses each of the four timing-points to modify the salary with an INSERT
, UPDATE
, or DELETE
statement. In the global declaration section, the initial salary is declared as 10,000
.
INSERT
the record into table emp
.
The INSERT
statement produces the following output:
The UPDATE
statement updates the employee salary record, setting the salary to 15000
for a specific employee number:
The UPDATE
statement produces the following output:
sql OUTPUT Before Statement: 11000 Before each row: 12000 After each row: 13000 After statement: 14000 UPDATE 1
SELECT * FROM emp; EMPNO | ENAME | SAL | DEPTNO -------+-------+-------+-------- 1111 | SMITH | 15000 | 20 (1 row)
The DELETE
statement produces the following output:
The TRUNCATE
statement removes all the records from the emp
table:
The TRUNCATE
statement produces the following output:
Note
You can use the TRUNCATE
statement only at a BEFORE STATEMENT
or AFTER STATEMENT
timing point.
This example creates a compound trigger named hr_trigger
on the emp
table. It is a WHEN
condition that checks and prints employee salary whenever an INSERT
, UPDATE
, or DELETE
statement affects the emp
table. The database evaluates the WHEN
condition for a row-level trigger, and the trigger executes once per row if the WHEN
condition evaluates to TRUE
. The statement-level trigger executes regardless of the WHEN
condition.
Insert the record into table emp
: