Scribd
Upload
51 views

DBMS Lab7

The document discusses MySQL triggers. It defines triggers as SQL statements that are automatically invoked when data is changed in an associated table via INSERT, UPDATE or DELETE statements. It provides examples of different trigger times - BEFORE and AFTER. It also illustrates the syntax for creating a trigger using the CREATE TRIGGER statement. As a practice problem, it demonstrates creating a BEFORE UPDATE trigger on a Customer table to log changes to a customer_audit table.

Uploaded by

Vipin Saraogi
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
51 views

DBMS Lab7

The document discusses MySQL triggers. It defines triggers as SQL statements that are automatically invoked when data is changed in an associated table via INSERT, UPDATE or DELETE statements. It provides examples of different trigger times - BEFORE and AFTER. It also illustrates the syntax for creating a trigger using the CREATE TRIGGER statement. As a practice problem, it demonstrates creating a BEFORE UPDATE trigger on a Customer table to log changes to a customer_audit table.

Uploaded by

Vipin Saraogi
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

BK BIRLA INSTITUE OF ENGINEERING & TECHNOLGY (BKBIET)

DBMS LAB SHEET VII

PROBLEM STATEMENT

TRIGGERS IN MySQL

What Is MySQL Triggers?

In MySQL, a trigger is a set of SQL statements that is invoked automatically when a change is made to the
data on the associated table. A trigger can be defined to be invoked either before or after the data is
changed by INSERT, UPDATE or DELETE statement. BEFORE INSERT – activated before data is inserted into
the table.

 AFTER INSERT – activated after data is inserted into the table.


 BEFORE UPDATE – activated before data in the table is updated.
 AFTER UPDATE – activated after data in the table is updated.
 BEFORE DELETE – activated before data is removed from the table.
 AFTER DELETE – activated after data is removed from the table.

When you use a statement that does not use INSERT, DELETE or UPDATE statement to change data in a
table, the triggers associated with the table are not invoked. For example, the TRUNCATE statement
removes all data of a table but does not invoke the trigger associated with that table.

There are some statements that use the INSERT statement behind the scenes such as REPLACE
statement or LOAD DATA statement. If you use these statements, the corresponding triggers associated
with the table are invoked.

You must use a unique name for each trigger associated with a table. However, you can have the same
trigger name defined for different tables though it is not a good practice.

MySQL trigger syntax

In order to create a new trigger, you use the CREATE TRIGGER statement. The following illustrates the
syntax of the CREATE TRIGGER statement:

CREATE TRIGGER trigger_name trigger_time trigger_event


ON table_name
FOR EACH ROW
BEGIN
...
END;
Let’s examine the syntax above in more detail.

 You put the trigger name after the CREATE TRIGGER statement. The trigger name should follow
the naming convention [trigger time]_[table name]_[trigger event], for
example before_employees_update.
 Trigger activation time can be BEFORE or AFTER. You must specify the activation time when you
define a trigger. You use the BEFORE keyword if you want to process action prior to the change is
made on the table and AFTER if you need to process action after the change is made.
 The trigger event can be INSERT, UPDATE or DELETE. This event causes the trigger to be invoked.
A trigger only can be invoked by one event. To define a trigger that is invoked by multiple events,
you have to define multiple triggers, one for each event.
 A trigger must be associated with a specific table. Without a table trigger would not exist
therefore you have to specify the table name after the ON keyword.
 You place the SQL statements between BEGIN and END block. This is where you define the logic
for the trigger.

PRACTICE PROBLEM

Create Table “Customer” with following schema.

Cid CHAR(4) Primary Key


Name VARCHAR(30) NOT NULL
Creditlimit INTEGER

Insert following values in Customer table.

Cid Name Creditlimit


1001 Aditya 20000
1002 Deepak 30000
1003 Harsh 40000
1004 Sunita 15000
1005 Vineeta 50000

Now, create a new table named customer_audit to keep the changes of the customer table.
SOLUTION

The following statement creates the customer_audit table.

CREATE TABLE customer_audit (


id INT AUTO_INCREMENT PRIMARY KEY,
customerId CHAR(4) NOT NULL,
changedat DATETIME DEFAULT NULL,
creditlimit INT,
action VARCHAR(50) DEFAULT NULL
);

Now, create a BEFORE UPDATE trigger that is invoked before a change is made to the customer table.

DELIMITER $$
CREATE TRIGGER before_customer_update
BEFORE UPDATE ON Customer
FOR EACH ROW
BEGIN
INSERT INTO customer_audit
SET action = 'update',
customerId = OLD.Cid,
creditlimit = OLD.CreditLimit,
changedat = NOW();
END$$
DELIMITER ;

To view all triggers in the current database, you use SHOW TRIGGERS statement as follows:

SHOW TRIGGERS;

After that, update the Customer table to check whether the trigger is invoked.

UPDATE Customer SET CreditLimit = 50000 WHERE Cid = ‘1001’;

Finally, to check if the trigger was invoked by the UPDATE statement, you can query the customer_aui
t table using the following query:

SELECT * FROM customer_audit;

You might also like