Trigger

Trigger
Trigger
• A trigger is a stored procedure in database which
automatically invokes whenever a special event occurs
in the database.
• A procedure that starts automatically if
specified changes occur to the DBMS.
• For example, a trigger can be invoked when a row is
inserted into a specified table or when certain table
columns are being updated.
Example: 1
Triggers (Active database)
• Three parts:
– Event (activates the trigger)
– Condition (tests whether the triggers should run)
[Optional]
– Action (what happens if the trigger runs)
• Semantics:
– When event occurs, and condition is satisfied, the
action is performed.
Triggers – Event,Condition,Action
• Eventscould be :
BEFORE|AFTER INSERT|UPDATE|DELETE ON <tableName>
e.g BEFORE INSERT ON Professor

.:
• Condition is SQL expression or even an SQL
query (query with non- empty result
means TRUE)
• Action can be many different choices :

– SQL statements , even DDL andtransaction-
oriented statements like “commit”.
Syntax:
create trigger [trigger_name]

[before | after]
{insert | update | delete}
on [table_name]
[for each row]
[trigger_body]
Example Trigger
Assume our DBhas a relation schema

:Professor( pNum, pName, salary)
We want to write a trigger that :
Ensures that any new professor inserted

has salary >= 60000
Example Trigger Even
t
CREATE TRIGGER minSalary “BEFORE INSERT” ON

Professor
for what context ?

Condition
BEGIN
check for violation here ?
END;
Example Trigger
CREATE TRIGGER minSalary BEFORE

INSERT ON Professor
FOR EACH ROW

trigger is performed
BEGIN for each row
inserted
Violation of Minimum Professor
Salary?
END;
Example Trigger
CREATE TRIGGER minSalary BEFORE INSERT ON
Professor
FOR EACH ROW
BEGIN
IF (:new.salary < 60000)

THEN RAISE_APPLICATION_ERROR (-20004,
‘Violation of Minimum
Professor Salary’);
END IF;
Details of Trigger Example
• BEFORE INSERT ON Professor
– This trigger is checked before the tuple is inserted
• FOREACH ROW
– specifies that trigger is performed for each row inserted
• : new
– refers to the new tuple inserted
• If (: new.salary < 60000)
– then an application error is raised and hence the row is not
inserted; otherwise the row is inserted.
• Use error code: -20004; When the procedure
raise_application_error executes, It halts the execution of the
current block immediately. It also reverses all changes made to
the OUT or IN OUT parameters.
– this is in the valid range
Condition
Example Trigger
Using Condition
CREATE TRIGGER minSalary BEFORE INSERT ON Professor
FOR EACH ROW
WHEN (new.salary < 60000)
BEGIN
RAISE_APPLICATION_ERROR (-20004,
‘Violation of Minimum Professor Salary’);
END;
• Conditions can refer to old/new values of tuples

modified by the statement activating the trigger.
Triggers: REFERENCING
CREATE TRIGGER minSalary BEFORE INSERT ON Professor
REFERENCING NEW as newTuple
FOR EACH ROW
WHEN (newTuple.salary < 60000)
BEGIN
‘Violation of Minimum Professor Salary’);
END;
Example Trigger
CREATE TRIGGER minSalary BEFORE UPDATE

ON Professor
REFERENCING OLD AS oldTuple NEW as newTuple FOR EACH
ROW
WHEN (newTuple.salary < oldTuple.salary) BEGIN
RAISE_APPLICATION_ERROR (-20004, ‘Salary
Decreasing !!’);
END;
• Ensure that salary does not

decrease
Another Trigger Example
CREATE TRIGGER YoungSailors Update

AFTER INSERT ON SAILORS
REFERENCING NEW TABLE AS NewSailors FOR
EACH STATEMENT
INSERT
INTO YoungSailors( sid, name, age, rating)
SELECT sid, name, age, rating
FROMNewSailors N
WHERE N.age <= 18
Combining multiple events into one
trigger
CREATE TRIGGER salaryRestrictions
AFTER INSERT OR UPDATE ON Professor
FOR EACH ROW
BEGIN
1 IF (INSERTING AND :new.salary < 60000) THEN
RAISE_APPLICATION_ERROR (-20004, 'below min
salary'); END IF;
2 IF (UPDATING AND :new.salary <
:old.salary) THEN
‘Salary Decreasing !!'); END IF;
END;
Summary :Trigger Syntax
CREATE TRIGGER <triggerName>
BEFORE|AFTER INSERT|DELETE|UPDATE
[OF <columnList>] ON <tableName>|<viewName>
[REFERENCING [OLD AS <oldName>] [NEW AS
<newName>]]
[FOR EACH ROW] (default is “FOR EACH STATEMENT”)
[WHEN (<condition>)]
< body>;
Purpose of Triggers
❖ To generate data automatically.

❖ To enforce complex integrity constraints.
❖ To customize complex security authorization.
❖ To maintain replicate tables.
❖ To audit data modifications.
Thank You

Trigger

Uploaded by

Trigger

Uploaded by

Trigger

e.g BEFORE INSERT ON Professor

• Action can be many different choices :

create trigger [trigger_name]

Assume our DBhas a relation schema

We want to write a trigger that :

Ensures that any new professor inserted

CREATE TRIGGER minSalary “BEFORE INSERT” ON

for what context ?

check for violation here ?

CREATE TRIGGER minSalary BEFORE

FOR EACH ROW

IF (:new.salary < 60000)

• Conditions can refer to old/new values of tuples

FOR EACH ROW

WHEN (newTuple.salary < 60000)

CREATE TRIGGER minSalary BEFORE UPDATE

• Ensure that salary does not

CREATE TRIGGER YoungSailors Update

❖ To generate data automatically.

You might also like