MySQL Stored Procedure

A procedure (often called a stored procedure) is a collection of pre-compiled SQL

statements stored inside the database. It is a subroutine or a subprogram in the regular
computing language. A procedure always contains a name, parameter lists, and SQL
statements. We can invoke the procedures by using triggers, other procedures and
applications such as Java, Python, PHP, etc. It was first introduced in MySQL version 5.
Presently, it can be supported by almost all relational database systems.

If we consider the enterprise application, we always need to perform specific tasks such
as database cleanup, processing payroll, and many more on the database regularly.
Such tasks involve multiple SQL statements for executing each task. This process might
easy if we group these tasks into a single task. We can fulfill this requirement
in MySQL by creating a stored procedure in our database.

A procedure is called a recursive stored procedure when it calls itself. Most database
systems support recursive stored procedures. But, it is not supported well in MySQL.

Stored Procedure Features

o Stored Procedure increases the performance of the applications. Once stored

procedures are created, they are compiled and stored in the database.
o Stored procedure reduces the traffic between application and database server.
Because the application has to send only the stored procedure's name and
parameters instead of sending multiple SQL statements.
o Stored procedures are reusable and transparent to any applications.
o A procedure is always secure. The database administrator can grant permissions
to applications that access stored procedures in the database without giving any
permissions on the database tables.

How to create a procedure?

The following syntax is used for creating a stored procedure in MySQL. It can return one
or more value through parameters or sometimes may not return at all. By default, a
procedure is associated with our current database. But we can also create it into another
database from the current database by specifying the name
as database_name.procedure_name. See the complete syntax:
 x
1. DELIMITER &&
2. CREATE PROCEDURE procedure_name [[IN | OUT | INOUT] parameter_name datatype [,
parameter datatype]) ]
3. BEGIN
4. Declaration_section
5. Executable_section
6. END &&
7. DELIMITER ;

Parameter Explanations
The procedure syntax has the following parameters:

Parameter Name Descriptions

procedure_name It represents the name of the stored procedure.

parameter It represents the number of parameters. It can be one or more than one.

Declaration_section It represents the declarations of all variables.

Executable_section It represents the code for the function execution.

MySQL procedure parameter has one of three modes:

IN parameter

It is the default mode. It takes a parameter as input, such as an attribute. When we

define it, the calling program has to pass an argument to the stored procedure. This
parameter's value is always protected.

OUT parameters

It is used to pass a parameter as output. Its value can be changed inside the stored
procedure, and the changed (new) value is passed back to the calling program. It is
noted that a procedure cannot access the OUT parameter's initial value when it starts.

INOUT parameters
 It is a combination of IN and OUT parameters. It means the calling program can pass the
argument, and the procedure can modify the INOUT parameter, and then passes the
new value back to the calling program.

How to call a stored procedure?

We can use the CALL statement to call a stored procedure. This statement returns the
values to its caller through its parameters (IN, OUT, or INOUT). The following syntax is
used to call the stored procedure in MySQL:

1. CALL procedure_name ( parameter(s))

Example
Let us understand how to create a procedure in MySQL through example. First, we need
to select a database that will store the newly created procedure. We can select the
database using the below statement:

1. mysql> USE database_name;

Suppose this database has a table named student_info that contains the following data:

Procedure without Parameter

Suppose we want to display all records of this table whose marks are greater than
70 and count all the table rows. The following code creates a procedure
named get_merit_students:
1. DELIMITER &&
2. CREATE PROCEDURE get_merit_student ()
3. BEGIN
4. SELECT * FROM student_info WHERE marks > 70;
5. SELECT COUNT(stud_code) AS Total_Student FROM student_info;
6. END &&
7. DELIMITER ;

If this code executed successfully, we would get the below output:

Let us call the procedure to verify the output:

1. mysql> CALL get_merit_student();

It will give the output as follows:

 Procedures with IN Parameter
In this procedure, we have used the IN parameter as 'var1' of integer type to accept a
number from users. Its body part fetches the records from the table using
a SELECT statement and returns only those rows that will be supplied by the user. It also
returns the total number of rows of the specified table. See the procedure code:

1. DELIMITER &&
2. CREATE PROCEDURE get_student (IN var1 INT)
3. BEGIN
4. SELECT * FROM student_info LIMIT var1;
5. SELECT COUNT(stud_code) AS Total_Student FROM student_info;
6. END &&
7. DELIMITER ;

After successful execution, we can call the procedure as follows:

1. mysql> CALL get_student(4);

We will get the below output:

 Procedures with OUT Parameter
In this procedure, we have used the OUT parameter as the 'highestmark' of integer
type. Its body part fetches the maximum marks from the table using a MAX() function.
See the procedure code:

1. DELIMITER &&
2. CREATE PROCEDURE display_max_mark (OUT highestmark INT)
3. BEGIN
4. SELECT MAX(marks) INTO highestmark FROM student_info;
5. END &&
6. DELIMITER ;

This procedure's parameter will get the highest marks from the student_info table.
When we call the procedure, the OUT parameter tells the database systems that its value
goes out from the procedures. Now, we will pass its value to a session variable @M in
the CALL statement as follows:

1. mysql> CALL display_max_mark(@M);

2. mysql> SELECT @M;

Here is the output:

 Procedures with INOUT Parameter
In this procedure, we have used the INOUT parameter as 'var1' of integer type. Its body
part first fetches the marks from the table with the specified id and then stores it into
the same variable var1. The var1 first acts as the IN parameter and then OUT parameter.
Therefore, we can call it the INOUT parameter mode. See the procedure code:

1. DELIMITER &&
2. CREATE PROCEDURE display_marks (INOUT var1 INT)
3. BEGIN
4. SELECT marks INTO var1 FROM student_info WHERE stud_id = var1;
5. END &&
6. DELIMITER ;

After successful execution, we can call the procedure as follows:

1. mysql> SET @M = '3';

2. mysql> CALL display_marks(@M);
3. mysql> SELECT @M;

We will get the below output:

 How to show or list stored procedures in MySQL?
When we have several procedures in the MySQL server, it is very important to list all
procedures. It is because sometimes the procedure names are the same in many
databases. In that case, this query is very useful. We can list all procedure stored on the
current MySQL server as follows:

1. SHOW PROCEDURE STATUS [LIKE 'pattern' | WHERE search_condition]

This statement displays all stored procedure names, including their characteristics.
If we want to display procedures in a particular database, we need to use
the WHERE clause. In case we want to list stored procedures with a specific word, we
need to use the LIKE clause.

We can list all stored procedure in the MySQL mystudentsb database using the below
statement:

1. mysql> SHOW PROCEDURE STATUS WHERE db = 'mystudentdb';

It will give the below output where we can see that the mystudentdb database
contains four stored procedures:
 How to delete/drop stored procedures in MySQL?
MySQL also allows a command to drop the procedure. When the procedure is dropped,
it is removed from the database server also. The following statement is used to drop a
stored procedure in MySQL:

1. DROP PROCEDURE [ IF EXISTS ] procedure_name;

Suppose we want to remove the procedure named display_marks from the

mystudentdb database. We can do this by first selecting the database and then use the
syntax as follows to remove the procedure:

1. mysql> DROP PROCEDURE display_marks;

We can verify it by listing the procedure in the specified database using the SHOW
PROCEDURE STATUS command. See the below output:

How to create a procedure in MySQL workbench?

We first launch the tool and log in with the username and password to create
procedures in the MySQL Workbench. Now, we need to do the following steps for
creating a stored procedure:
1. Go to the Navigation tab and click on the Schema menu where all the previously
created databases available. Select your desired database (for example, employeedb). It
will pop up the following options.

2. Right-click on the Stored Procedure, and we will get the default procedure code. See
the below screen:

3. Complete the procedure code and click on the Apply button. In the next window, we
will review the procedure code once again, and if no error was found, click on the Apply
button.
4. After clicking on the Apply button, click on the Finish button for completion.

5. We can navigate to the schema menu again to verify this newly created procedure. It
means first select your database and expand it to display its sub-menu. In the sub-
menu, expanding the stored procedure option will show the newly created procedure.
See the below image:

6. We can call the procedure by tapping on the red rectangle box or simply execute the
CALL statement.

How to alter the procedure in MySQL?

MySQL does not allow any command to alter the procedure in MySQL. However, it
provides a command that is used to change the characteristics of a stored procedure.
This command may alter more than one change in the procedure but does not modify
the stored procedure's parameters or body. If we want to make such changes, we
 must drop and re-create the procedure using the DROP PROCEDURE and CREATE
PROCEDURE statement.

The below statement is used to change the characteristics of a procedure but not
the actual procedure:

1. ALTER PROCEDURE procedure_name [characteristics ...]

2.
3. characteristics: {
4. COMMENT 'string'
5. | LANGUAGE SQL
6. | { CONTAINS SQL | NO SQL | READS SQL DATA | MODIFIES SQL DATA }
7. | SQL SECURITY { DEFINER | INVOKER }
8. }

Suppose we want to add a comment to the existing procedure. In such a case, we can
use the ALTER statement as follows to accomplish this task:

1. mysql> ALTER PROCEDURE get_merit_student

2. COMMENT 'It displays all records';

After executing this statement, we can verify it by using the below statement:

1. mysql> SHOW CREATE PROCEDURE get_merit_student \G;

It will display the below output where we can see that the comment is added
successfully.
It is to note that we can alter the body of the stored procedure in MySQL using the
workbench tool. So open this tool, navigate to the schema menu, and expand the
database that contains stored procedures. Now, select your procedure, right-click on it
and choose ALTER STORED PROCEDURE option. See the below screen:

After clicking this option, we will get a window that contains a procedure code. See the
below screen that contains procedure code to display all employee:
 Now, we will modify this code. Suppose we want to display only male employees. To do
this, we can change this code from the below code and click on the Apply button:

1. SELECT * FROM employee WHERE gender = 'M';

In this window, we will review the procedure code once again, and if no error was found,
click on the Apply -> Apply -> Finish button to complete the process.

Drawbacks of Using Stored Procedures

o If we use stored procedures, the memory uses of every connection that uses
those stored procedures will increase substantially. Also, if we overuse many
logical applications inside stored procedures, the CPU usage will increase. It is
because the database server is not well designed for logical operations.
o Stored procedure's constructs are not designed to develop complex and flexible
business logic.
o It is difficult to debug stored procedures. Only a few database management
systems allow us to debug stored procedures. Unfortunately, MySQL does not
provide facilities for debugging stored procedures.
o It is not easy to develop and maintain stored procedures. Developing and
maintaining stored procedures are often required a specialized skill set that not
all application developers possess. It may lead to problems in both application
development and maintenance phases.

MySQL Trigger
A trigger in MySQL is a set of SQL statements that reside in a system catalog. It is a
special type of stored procedure that is invoked automatically in response to an
event. Each trigger is associated with a table, which is activated on any DML statement
such as INSERT, UPDATE, or DELETE.

A trigger is called a special procedure because it cannot be called directly like a stored
procedure. The main difference between the trigger and procedure is that a trigger is
called automatically when a data modification event is made against a table. In contrast,
a stored procedure must be called explicitly.

Generally, triggers are of two types according to the SQL standard: row-level triggers
and statement-level triggers.

Row-Level Trigger: It is a trigger, which is activated for each row by a triggering

statement such as insert, update, or delete. For example, if a table has inserted, updated,
or deleted multiple rows, the row trigger is fired automatically for each row affected by
the insert, update, or delete statement.

Statement-Level Trigger: It is a trigger, which is fired once for each event that occurs
on a table regardless of how many rows are inserted, updated, or deleted.

NOTE: We should know that MySQL doesn't support statement-level triggers. It

provides supports for row-level triggers only.

Why we need/use triggers in MySQL?

We need/use triggers in MySQL due to the following features:

o Triggers help us to enforce business rules.

o Triggers help us to validate data even before they are inserted or updated.
o Triggers help us to keep a log of records like maintaining audit trails in tables.
o SQL triggers provide an alternative way to check the integrity of data.
o Triggers provide an alternative way to run the scheduled task.
o Triggers increases the performance of SQL queries because it does not need to compile
each time the query is executed.
o Triggers reduce the client-side code that saves time and effort.
o Triggers help us to scale our application across different platforms.
o Triggers are easy to maintain.

Limitations of Using Triggers in MySQL

o MySQL triggers do not allow to use of all validations; they only provide extended
validations. For example, we can use the NOT NULL, UNIQUE, CHECK and FOREIGN KEY
constraints for simple validations.
o Triggers are invoked and executed invisibly from the client application. Therefore, it isn't
easy to troubleshoot what happens in the database layer.
o Triggers may increase the overhead of the database server.

Types of Triggers in MySQL?

 We can define the maximum six types of actions or events in the form of triggers:

1. Before Insert: It is activated before the insertion of data into the table.
2. After Insert: It is activated after the insertion of data into the table.
3. Before Update: It is activated before the update of data in the table.
4. After Update: It is activated after the update of the data in the table.
5. Before Delete: It is activated before the data is removed from the table.
6. After Delete: It is activated after the deletion of data from the table.

When we use a statement that does not use INSERT, UPDATE or DELETE query to
change the data in a table, the triggers associated with the trigger will not be invoked.

Naming Conventions
Naming conventions are the set of rules that we follow to give appropriate unique
names. It saves our time to keep the work organize and understandable. Therefore, we
must use a unique name for each trigger associated with a table. However, it is a
good practice to have the same trigger name defined for different tables.

The following naming convention should be used to name the trigger in MySQL:

1. (BEFOR | AFTER) table_name (INSERT | UPDATE | DELETE)

Thus,

Trigger Activation Time: BEFORE | AFTER

Trigger Event: INSERT | UPDATE | DELETE

How to create triggers in MySQL?

We can use the CREATE TRIGGER statement for creating a new trigger in MySQL. Below
is the syntax of creating a trigger in MySQL:

1. CREATE TRIGGER trigger_name

2. (AFTER | BEFORE) (INSERT | UPDATE | DELETE)
3. ON table_name FOR EACH ROW
4. BEGIN
5. --variable declarations
6. --trigger code
7. END;

MySQL Create Trigger

In this article, we are going to learn how to create the first trigger in MySQL. We can
create a new trigger in MySQL by using the CREATE TRIGGER statement. It is to ensure
that we have trigger privileges while using the CREATE TRIGGER command. The
following is the basic syntax to create a trigger:

1. CREATE TRIGGER trigger_name trigger_time trigger_event

2. ON table_name FOR EACH ROW
3. BEGIN
4. --variable declarations
5. --trigger code
6. END;

Parameter Explanation
The create trigger syntax contains the following parameters:

trigger_name: It is the name of the trigger that we want to create. It must be written
after the CREATE TRIGGER statement. It is to make sure that the trigger name should be
unique within the schema.

trigger_time: It is the trigger action time, which should be either BEFORE or AFTER. It is
the required parameter while defining a trigger. It indicates that the trigger will be
invoked before or after each row modification occurs on the table.

trigger_event: It is the type of operation name that activates the trigger. It can be
either INSERT, UPDATE, or DELETE operation. The trigger can invoke only one event at
one time. If we want to define a trigger which is invoked by multiple events, it is
required to define multiple triggers, and one for each event.

table_name: It is the name of the table to which the trigger is associated. It must be
written after the ON keyword. If we did not specify the table name, a trigger would not
exist.
 BEGIN END Block: Finally, we will specify the statement for execution when the trigger
is activated. If we want to execute multiple statements, we will use the BEGIN END block
that contains a set of queries to define the logic for the trigger.

The trigger body can access the column's values, which are affected by the DML
statement. The NEW and OLD modifiers are used to distinguish the column
values BEFORE and AFTER the execution of the DML statement. We can use the column
name with NEW and OLD modifiers as OLD.col_name and NEW.col_name. The
OLD.column_name indicates the column of an existing row before the updation or
deletion occurs. NEW.col_name indicates the column of a new row that will be inserted
or an existing row after it is updated.

For example, suppose we want to update the column name message_info using the
trigger. In the trigger body, we can access the column value before the update
as OLD.message_info and the new value NEW.message_info.

We can understand the availability of OLD and NEW modifiers with the below table:

Trigger Event OLD NEW

INSERT No Yes

UPDATE Yes Yes

ELETE Yes No

MySQL Trigger Example

Let us start creating a trigger in MySQL that makes modifications in the employee table.
First, we will create a new table named employee by executing the below statement:

1. CREATE TABLE employee(

2. name varchar(45) NOT NULL,
3. occupation varchar(35) NOT NULL,
4. working_date date,
5. working_hours varchar(10)
6. );

Next, execute the below statement to fill the records into the employee table:
1. INSERT INTO employee VALUES
2. ('Robin', 'Scientist', '2020-10-04', 12),
3. ('Warner', 'Engineer', '2020-10-04', 10),
4. ('Peter', 'Actor', '2020-10-04', 13),
5. ('Marco', 'Doctor', '2020-10-04', 14),
6. ('Brayden', 'Teacher', '2020-10-04', 12),
7. ('Antonio', 'Business', '2020-10-04', 11);

Next, execute the SELECT statement to verify the inserted record:

Next, we will create a BEFORE INSERT trigger. This trigger is invoked automatically
insert the working_hours = 0 if someone tries to insert working_hours < 0.

1. mysql> DELIMITER //
2. mysql> Create Trigger before_insert_empworkinghours
3. BEFORE INSERT ON employee FOR EACH ROW
4. BEGIN
5. IF NEW.working_hours < 0 THEN SET NEW.working_hours = 0;
6. END IF;
7. END //

If the trigger is created successfully, we will get the output as follows:

 Now, we can use the following statements to invoke this trigger:

1. mysql> INSERT INTO employee VALUES

2. ('Markus', 'Former', '2020-10-08', 14);
3.
4. mysql> INSERT INTO employee VALUES
5. ('Alexander', 'Actor', '2020-10-012', -13);

After execution of the above statement, we will get the output as follows:
 In this output, we can see that on inserting the negative values into the working_hours
column of the table will automatically fill the zero value by a trigger.

MySQL Show/List Triggers

The show or list trigger is much needed when we have many databases that contain
various tables. Sometimes we have the same trigger names in many databases; this
query plays an important role in that case. We can get the trigger information in the
database server using the below statement. This statement returns all triggers in all
databases:

1. mysql> SHOW TRIGGERS;

The following steps are necessary to get the list of all triggers:

Step 1: Open the MySQL Command prompt and logged into the database server using
the password that you have created during MySQL's installation. After a successful
connection, we can execute all the SQL statements.

Step 2: Next, choose the specific database by using the command below:

Play Video
x

1. mysql> USE database_name;

Step 3: Finally, execute the SHOW TRIGGERS command.

Let us understand it with the example given below. Suppose we have a database
name "mysqltestdb" that contains many tables. Then execute the below statement to
list the triggers:

1. mysql> USE mysqltestdb;

2. mysql>SHOW TRIGGERS;

The following output explains it more clearly:

 If we want to show or list the trigger information in a specific database from the current
database without switching, MySQL allows us to use the FROM or IN clause, followed
by the database name. The following statement explains it more clearly:

1. mysql> SHOW TABLES IN database_name;

The above statement can also be written as:

1. mysql> SHOW TABLES FROM database_name;

When we execute the above statements, we will get the same result.

Show Triggers Using Pattern Matching

MySQL also provides a LIKE clause option that enables us to filter the trigger name
using different pattern matching. The following is the syntax to use pattern matching
with show trigger command:

1. mysql> SHOW TRIGGERS LIKE pattern;

2. OR,
3. mysql> SHOW TRIGGERS FROM database_name LIKE pattern;
 If we want to list/show trigger names based on specific search condition, we can use
the WHERE clause as follows:

1. mysql> SHOW TRIGGERS WHERE search_condition;

2. OR,
3. mysql> SHOW TRIGGERS FROM database_name WHERE search_condition;

Example
Suppose we want to show all triggers that belongs to the employee table, execute the
statement as follows:

1. mysql> SHOW TRIGGERS FROM mysqltestdb WHERE table = 'employee';

We will get the output as follows:

NOTE: It is to note that we must have a SUPER privilege to execute the SHOW
TRIGGERS statement.

The show trigger statement contains several columns in the result set. Let us explain
each column in detail.

o Trigger: It is the name of the trigger that we want to create and must be unique within
the schema.
o Event: It is the type of operation name that invokes the trigger. It can be either INSERT,
UPDATE, or DELETE operation.
o Table: It is the name of the table to which the trigger belongs.
o Statement: It is the body of the trigger that contains logic for the trigger when it
activates.
o Timing: It is the activation time of the trigger, either BEFORE or AFTER. It indicates that
the trigger will be invoked before or after each row of modifications occurs on the table.
o Created: It represents the time and date when the trigger is created.
 o sql_mode: It displays the SQL_MODE when the trigger is executed.
o Definer: It is the name of a user account that created the trigger and should be in the
'user_name'@'host_name' format.
o character_set_client: It was the session value of the character_set_client system variable
when the trigger was created.
o collation_connection: It was the session value of the character_set_client system
variable when the trigger was created.
o Database Collation: It determines the rules that compare and order the character string.
It is the collation of the database with which the trigger belongs.

How to show triggers in MySQL workbench?

It is a visual GUI tool used to create databases, tables, indexes, views, and stored
procedures quickly and efficiently. To show a trigger using this tool, we first need to
launch the MySQL Workbench and log in using the username and password that we
have created earlier. We will get the screen as follows:
Now do the following steps to show triggers:

1. Go to the Navigation tab and click on the Schema menu that contains all the
databases available in the MySQL server.

2. Select the database (for example, mysqltestdb), double click on it, and show the sub-
menu containing Tables, Views, Functions, and Stored Procedures. See the below
screen.
3. Click on the Tables sub-menu and select the table on which you have created a
trigger. See the below image:

4. Clicking on the Triggers sub-menu, we can see all triggers associated with the
selected table. See the below image.
 MySQL DROP Trigger
We can drop/delete/remove a trigger in MySQL using the DROP TRIGGER statement. You
must be very careful while removing a trigger from the table. Because once we have deleted the
trigger, it cannot be recovered. If a trigger is not found, the DROP TRIGGER statement throws
an error.

MySQL allows us to drop/delete/remove a trigger mainly in two ways:

1. MySQL Command Line Client

2. MySQL Workbench

MySQL Command Line Client

We can drop an existing trigger from the database by using the DROP TRIGGER statement with
the below syntax:

1. DROP TRIGGER [IF EXISTS] [schema_name.]trigger_name;

Parameter Explanation

The parameters used in the drop trigger syntax are explained as follows:

Parameter Descriptions

Trigger_name It is the name of a trigger that we want to remove from the database server. It is a require
parameter.

Schema_nam It is the database name to which the trigger belongs. If we skip this parameter, the statemen
e will remove the trigger from the current database.

IF_EXISTS It is an optional parameter that conditionally removes triggers only if they exist on th
database server.

If we remove the trigger that does not exist, we will get an error. However, if we have specified
the IF EXISTS clause, MySQL gives a NOTE instead of an error.
 It is to note that we must have TRIGGER privileges before executing the DROP TRIGGER
statement for the table associated with the trigger. Also, removing a table will automatically
delete all triggers associated with the table.

MySQL DROP Trigger Example

Let us see how we can drop the trigger associated with the table through an example. So first, we
will display all triggers available in the selected database using the below statement:

1. mysql> SHOW TRIGGERS IN employeedb;

After executing the statement, we can see that there are two triggers
named before_update_salaries and sales_info_before_update. See the below image:

If we want to remove the before_update_salaries trigger, execute the below statement:

1. mysql> DROP TRIGGER employeedb.before_update_salaries;

It will successfully delete a trigger from the database. If we execute the above statement again, it
will return an error message. See the output:

If we execute the above statement again with an IF EXISTS clause, it will return the warning
message instead of producing an error. See the output:

1. mysql> DROP TRIGGER IF EXISTS employeedb.before_update_salaries;

We can execute the SHOW WARNING statement that generates a NOTE for a non-existent
trigger when using IF EXISTS. See the output:

How to Drop trigger in MySQL workbench?

To create an AFTER UPDATE trigger in workbench, we first launch the MySQL
Workbench and log in using the username and password. We will get the UI as follows:
Now do the following steps to delete or destroy a trigger associated with the table:

1. Go to the Navigation tab and click on the Schema menu. It will display all databases
available in the MySQL database server.
2. Select the database (for example, mystudentdb). Then, double click on the selected schema.
It displays the sub-menu containing Tables, Views, Functions, and Stored Procedures. See the
below screen.

3. Expand the Tables sub-menu and select a table on which a trigger is associated. Again expand
the selected Table -> Triggers; we will get the below image:

4. Now, right-click on the selected table and choose the Alter Table option that gives the screen
as below:
5. Now, click on the Trigger tab shown in the previous section's red rectangular box. You
will notice that there is a (+) and (-) icon button to add or delete a trigger:

6. Now, clicking on the (-) button will permanently remove the trigger associated with
the table.
 MySQL BEFORE INSERT TRIGGER
Before Insert Trigger in MySQL is invoked automatically whenever an insert operation is
executed. In this article, we are going to learn how to create a before insert trigger with
its syntax and example.

Syntax
The following is the syntax to create a BEFORE INSERT trigger in MySQL:

1. CREATE TRIGGER trigger_name

2. BEFORE INSERT
3. ON table_name FOR EACH ROW
4. Trigger_body ;

The BEFORE INSERT trigger syntax parameter can be explained as below:

o First, we will specify the name of the trigger that we want to create. It should be
unique within the schema.
o Second, we will specify the trigger action time, which should be BEFORE INSERT.
This trigger will be invoked before each row modifications occur on the table.
o Third, we will specify the name of a table to which the trigger is associated. It
must be written after the ON keyword. If we did not specify the table name, a
trigger would not exist.
o Finally, we will specify the statement for execution when the trigger is activated.

If we want to execute multiple statements, we will use the BEGIN END block that
contains a set of queries to define the logic for the trigger. See the below syntax:

x
1. DELIMITER $$
2. CREATE TRIGGER trigger_name BEFORE INSERT
3. ON table_name FOR EACH ROW
4. BEGIN
5. variable declarations
6. trigger code
7. END$$
8. DELIMITER ;

Restrictions

o We can access and change the NEW values only in a BEFORE INSERT trigger.
o We cannot access the OLD If we try to access the OLD values, we will get an error
because OLD values do not exist.
o We cannot create a BEFORE INSERT trigger on a VIEW.

BEFORE INSERT Trigger Example

Let us understand how to create a BEFORE INSERT trigger using the CREATE TRIGGER
statement in MySQL with an example.

Suppose we have created a table named employee as follows:

1. CREATE TABLE employee(

2. name varchar(45) NOT NULL,
3. occupation varchar(35) NOT NULL,
4. working_date date,
5. working_hours varchar(10)
6. );

Next, we will insert some records into the employee table and then execute the SELECT
statement to see the table data as follows:
 Next, we will use a CREATE TRIGGER statement to create a BEFORE INSERT trigger. This
trigger is invoked automatically that inserts the occupation = 'Leader' if someone tries
to insert the occupation = 'Scientist'.

1. mysql> DELIMITER //
2. mysql> Create Trigger before_insert_occupation
3. BEFORE INSERT ON employee FOR EACH ROW
4. BEGIN
5. IF NEW.occupation = 'Scientist' THEN SET NEW.occupation = 'Doctor';
6. END IF;
7. END //

If the trigger is created successfully, we will get the output as follows:

How to call the BEFORE INSERT trigger?

We can use the following statements to invoke the above-created trigger:

1. mysql> INSERT INTO employee VALUES

2. ('Markus', 'Scientist', '2020-10-08', 14);
3.
4. mysql> INSERT INTO employee VALUES
5. ('Alexander', 'Actor', '2020-10-012', 13);

After execution of the above statement, we will get the output as follows:
Execute the SELECT statement to verify the output:

In this output, we can see that on inserting the occupation column values as 'Scientist',
the table will automatically fill the 'Doctor' value by invoking a trigger.

How to create BEFORE INSERT Trigger in MySQL

workbench?
To create a before insert trigger using this tool, we first need to launch the MySQL
Workbench and log in using the username and password we created earlier. We will get
the screen as follows:
Now do the following steps for creating BEFORE INSERT trigger:

1. Go to the Navigation tab and click on the Schema menu that contains all the
databases available in the MySQL server.

2. Select the database (for example, mysqltestdb), double click on it. It will show
the sub-menu containing Tables, Views, Functions, and Stored Procedures. See the
below screen.
3. Expand the Tables sub-menu and select the table on which you want to create a
trigger. After selecting a table, right-click on the selected table (for example, employee),
and then click on the Alter Table option. See the below image:

4. Clicking on the Alter Table option gives the screen as below:

5. Now, click on the Trigger tab shown in the previous section's red rectangular box,
then select the Timing/Event BEFORE INSERT. We will notice that there is a (+) icon
button to add a trigger. Clicking on that button, we will get a default code on the trigger
based on choosing Timing/Event:
6. Now, complete the trigger code, review them once again, and no error found, click on
the Apply button.
7. After clicking on the Apply button, click on the Finish button for completion.
8. If we take at the schema menu, we will see employee_BEFORE_INSERT trigger under
the employee table as follows:
 MySQL AFTER INSERT Trigger
After Insert Trigger in MySQL is invoked automatically whenever an insert event occurs
on the table. In this article, we are going to learn how to create an after insert trigger
with its syntax and example.

Syntax
The following is the syntax to create an AFTER INSERT trigger in MySQL:

1. CREATE TRIGGER trigger_name

2. AFTER INSERT
3. ON table_name FOR EACH ROW
4. trigger_body ;

The AFTER INSERT trigger syntax parameter can be explained as below:

o First, we will specify the name of the trigger that we want to create. It should be
unique within the schema.
o Second, we will specify the trigger action time, which should be AFTER INSERT
clause to invoke the trigger.
o Third, we will specify the name of a table to which the trigger is associated. It
must be written after the ON keyword. If we did not specify the table name, a
trigger would not exist.
o Finally, we will specify the trigger body that contains one or more statements for
execution when the trigger is activated.

If we want to execute multiple statements, we will use the BEGIN END block that
contains a set of SQL queries to define the logic for the trigger. See the below syntax:

1. DELIMITER $$
2. CREATE TRIGGER trigger_name AFTER INSERT
3. ON table_name FOR EACH ROW
4. BEGIN
5. variable declarations
6. trigger code
7. END$$
8. DELIMITER ;

Restrictions

o We can access the NEW values but cannot change them in an AFTER INSERT
trigger.
o We cannot access the OLD If we try to access the OLD values, we will get an error
because there is no OLD on the INSERT trigger.
o We cannot create the AFTER INSERT trigger on a VIEW.

AFTER INSERT Trigger Example

Let us understand how to create an AFTER INSERT trigger using the CREATE
TRIGGER statement in MySQL with an example.

Suppose we have created a table named "student_info" as follows:

1. CREATE TABLE student_info (

2. stud_id int NOT NULL,
3. stud_code varchar(15) DEFAULT NULL,
4. stud_name varchar(35) DEFAULT NULL,
5. subject varchar(25) DEFAULT NULL,
6. marks int DEFAULT NULL,
7. phone varchar(15) DEFAULT NULL,
8. PRIMARY KEY (stud_id)
9. )

Next, we will insert some records into this table and then execute the SELECT
statement to see the table data as follows:
 Again, we will create a new table named "student_detail" as follows:

1. CREATE TABLE student_detail (

2. stud_id int NOT NULL,
3. stud_code varchar(15) DEFAULT NULL,
4. stud_name varchar(35) DEFAULT NULL,
5. subject varchar(25) DEFAULT NULL,
6. marks int DEFAULT NULL,
7. phone varchar(15) DEFAULT NULL,
8. Lasinserted Time,
9. PRIMARY KEY (stud_id)
10. );

Next, we will use a CREATE TRIGGER statement to create an after_insert_details trigger

on the student_info table. This trigger will be fired after an insert operation is
performed on the table.

1. mysql> DELIMITER //
2. mysql> Create Trigger after_insert_details
3. AFTER INSERT ON student_info FOR EACH ROW
4. BEGIN
5. INSERT INTO student_detail VALUES (new.stud_id, new.stud_code,
6. new.stud_name, new.subject, new.marks, new.phone, CURTIME());
7. END //
 If the trigger is created successfully, we will get the output as follows:

How to call the AFTER INSERT trigger?

We can use the following statements to invoke the above-created trigger:

1. mysql> INSERT INTO student_info VALUES

2. (10, 110, 'Alexandar', 'Biology', 67, '2347346438');

The table that has been modified after the update query executes is student_detail. We
can verify it by using the SELECT statement as follows:

1. mysql> SELECT * FROM student_detail;

In this output, we can see that on inserting values into the student_info table, the
student_detail table will automatically fill the records by invoking a trigger.

How to create AFTER INSERT Trigger in MySQL

workbench?
To create an after insert trigger using this tool, we first need to launch the MySQL
Workbench and log in using the username and password that we have created earlier.
We will get the screen as follows:

Now do the following steps for creating an AFTER INSERT trigger:

1. Go to the Navigation tab and click on the Schema menu that contains all the
databases available in the MySQL server.

2. Select the database (for example, mystudentdb), double click on it that shows
the sub-menu containing Tables, Views, Functions, and Stored Procedures. See the
below screen.
3. Expand the Tables sub-menu and select the table on which you want to create a
trigger. After selecting a table, right-click on the selected table (for example,
mystudentdb), and then click on the Alter Table option. See the below image:

4. Clicking on the Alter Table option gives the screen as below:

5. Now, click on the Trigger tab shown in the red rectangular box of the previous
section, then select the Timing/Event AFTER INSERT. We will notice that there is a (+)
icon button to add a trigger. Clicking on that button, we will get a default code on the
trigger based on choosing Timing/Event:

6. Now, complete the trigger code, review them once again, and if no error is found,
click on the Apply button.
7. After clicking on the Apply button, click on the Finish button for completion.
8. If we look at the schema menu, we can see AFTER_INSERT_detail trigger under
the student_info table as follows:

MySQL BEFORE UPDATE Trigger

 BEFORE UPDATE Trigger in MySQL is invoked automatically whenever an update
operation is fired on the table associated with the trigger. In this article, we are going to
learn how to create a before update trigger with its syntax and example.

Syntax
The following is the syntax to create a BEFORE UPDATE trigger in MySQL:

1. CREATE TRIGGER trigger_name

2. BEFORE UPDATE
3. ON table_name FOR EACH ROW
4. trigger_body ;

The BEFORE UPDATE trigger syntax parameter are explained as below:

o First, we will specify the trigger name that we want to create. It should be unique
within the schema.
o Second, we will specify the trigger action time, which should be BEFORE
UPDATE. This trigger will be invoked before each row of alterations occurs on the
table.
o Third, we will specify the name of a table to which the trigger is associated. It
must be written after the ON keyword. If we did not specify the table name, a
trigger would not exist.
o Finally, we will specify the trigger body that contains a statement for execution
when the trigger is activated.

If we want to execute multiple statements, we will use the BEGIN END block that
contains a set of queries to define the logic for the trigger. See the below syntax:

1. DELIMITER $$
2. CREATE TRIGGER trigger_name BEFORE UPDATE
3. ON table_name FOR EACH ROW
4. BEGIN
5. variable declarations
6. trigger code
7. END$$
8. DELIMITER ;

Restrictions

o We cannot update the OLD values in a BEFORE UPDATE trigger.

o We can change the NEW values.
o We cannot create a BEFORE UPDATE trigger on a VIEW.

BEFORE UPDATE Trigger Example

Let us understand how to create a BEFORE UPDATE trigger using the CREATE TRIGGER
statement in MySQL with an example.

Suppose we have created a table named sales_info as follows:

1. CREATE TABLE sales_info (

2. id INT AUTO_INCREMENT,
3. product VARCHAR(100) NOT NULL,
4. quantity INT NOT NULL DEFAULT 0,
5. fiscalYear SMALLINT NOT NULL,
6. CHECK(fiscalYear BETWEEN 2000 and 2050),
7. CHECK (quantity >=0),
8. UNIQUE(product, fiscalYear),
9. PRIMARY KEY(id)
10. );

Next, we will insert some records into the sales_info table as follows:

1. INSERT INTO sales_info(product, quantity, fiscalYear)

2. VALUES
3. ('2003 Maruti Suzuki',110, 2020),
4. ('2015 Avenger', 120,2020),
5. ('2018 Honda Shine', 150,2020),
6. ('2014 Apache', 150,2020);

Then, execute the SELECT statement to see the table data as follows:
 Next, we will use a CREATE TRIGGER statement to create a BEFORE UPDATE trigger.
This trigger is invoked automatically before an update event occurs in the table.

1. DELIMITER $$
2.
3. CREATE TRIGGER before_update_salesInfo
4. BEFORE UPDATE
5. ON sales_info FOR EACH ROW
6. BEGIN
7. DECLARE error_msg VARCHAR(255);
8. SET error_msg = ('The new quantity cannot be greater than 2 times the current quanti
ty');
9. IF new.quantity > old.quantity * 2 THEN
10. SIGNAL SQLSTATE '45000'
11. SET MESSAGE_TEXT = error_msg;
12. END IF;
13. END $$
14.
15. DELIMITER ;

If the trigger is created successfully, we will get the output as follows:

 The trigger produces an error message and stops the updation if we update the value in
the quantity column to a new value two times greater than the current value.

Let us understand the created trigger in details:

First, we have specified the trigger name as befor_update_salesInfo in the CREATE

TRIGGER clause. Second, specify the triggering event and then the table name on which
the trigger is associated. Third, we have declared a variable and set its value. Finally, we
have specified the trigger body that checks if the new value is two times greater than
the old value and then raises an error.

How to call the BEFORE UPDATE trigger?

First, we can use the following statements that update the quantity of the row whose id
= 2:

1. mysql> UPDATE sales_info SET quantity = 125 WHERE id = 2;

This statement works well because it does not violate the rule. Next, we will execute the
below statements that update the quantity of the row as 600 whose id = 2

1. mysql> UPDATE sales_info SET quantity = 600 WHERE id = 2;

It will give the error as follows because it violates the rule. See the below output.
How to create BEFORE UPDATE Trigger in MySQL
workbench?
To create a BEFORE UPDATE trigger using MySQL workbench, we first need to launch it
and then log in using the username and password we created earlier. We will get the
screen as follows:

Now do the following steps for creating BEFORE UPDATE trigger:

1. Go to the Navigation tab and click on the Schema menu that contains all the
databases available in the MySQL server.

2. Select the database (for example, employeedb), double click on it, and display
the sub-menu containing Tables, Views, Functions, and Stored Procedures. See the
below screen.

3. Expand the Tables sub-menu and select the table on which you want to create a
trigger. After selecting a table, right-click on the selected table (for example, sales_info),
and then click on the Alter Table option. See the below image:
4. Clicking on the Alter Table option gives the screen as below:
5. Now, click on the Trigger tab shown in the previous section's red rectangular box,
then select the Timing/Event BEFORE UPDATE. We will notice that there is a (+) icon
button to add a trigger. Clicking on that button, we will get a default code on trigger
based on choosing Timing/Event:
6. Now, complete the trigger code, review them once again, and if no error is found,
click on the Apply button.

7. After clicking on the Apply button, click on the Finish button for completion.
8. If we take at the schema menu, we will see
the trigger sales_info_before_update under the sales_info table as follows:
 MySQL AFTER UPDATE TRIGGER
The AFTER UPDATE trigger in MySQL is invoked automatically whenever an UPDATE
event is fired on the table associated with the triggers. In this article, we are going to
learn how to create an AFTER UPDATE trigger with its syntax and example.

Syntax
The following is the syntax to create an AFTER UPDATE trigger in MySQL:

1. CREATE TRIGGER trigger_name

2. AFTER UPDATE
3. ON table_name FOR EACH ROW
4. trigger_body ;

We can explain the parameters of AFTER UPDATE trigger syntax as below:

o First, we will specify the trigger name that we want to create. It should be unique
within the schema.
o Second, we will specify the trigger action time, which should be AFTER UPDATE.
This trigger will be invoked after each row of alterations occurs on the table.
o Third, we will specify the table name to which the trigger is associated. It must
be written after the ON If we did not specify the table name, a trigger would not
exist.
o Finally, we will specify the trigger body that contains a statement for execution
when the trigger is activated.

If we want to execute more than one statement, we will use the BEGIN END block that
contains a set of SQL queries to define the logic for the trigger. See the below syntax:

1. DELIMITER $$
2. CREATE TRIGGER trigger_name AFTER UPDATE
3. ON table_name FOR EACH ROW
4. BEGIN
5. variable declarations
6. trigger code
7. END$$
8. DELIMITER ;

Restrictions

o We can access the OLD rows but cannot update them.

o We can access the NEW rows but cannot update them.
o We cannot create an AFTER UPDATE trigger on a VIEW.

AFTER UPDATE Trigger Example

Let us understand how to create an AFTER UPDATE trigger using the CREATE TRIGGER
statement in MySQL with an example.

Suppose we have created a table named students to store the student's information as
follows:

1. mysql> CREATE TABLE students(

2. id int NOT NULL AUTO_INCREMENT,
3. name varchar(45) NOT NULL,
4. class int NOT NULL,
5. email_id varchar(65) NOT NULL,
6. PRIMARY KEY (id)
7. );

Next, we will insert some records into this table using the below statement:

1. INSERT INTO students (name, class, email_id)

2. VALUES ('Stephen', 6, '[email protected]'),
3. ('Bob', 7, '[email protected]'),
4. ('Steven', 8, '[email protected]'),
5. ('Alexandar', 7, '[email protected]');

Execute the SELECT query to see the table data.

 Third, we will create another table named students_log that keeps the updated
information in the selected user.

1. mysql> CREATE TABLE students_log(

2. user varchar(45) NOT NULL,
3. descreptions varchar(65) NOT NULL
4. );

We will then create an AFTER UPDATE trigger that promotes all students in the next
class, i.e., 6 will be 7, 7 will be 8, and so on. Whenever an updation is performed on a
single row in the "students" table, a new row will be inserted in the "students_log"
table. This table keeps the current user id and a description regarding the current
update. See the below trigger code.

1. DELIMITER $$
2.
3. CREATE TRIGGER after_update_studentsInfo
4. AFTER UPDATE
5. ON students FOR EACH ROW
6. BEGIN
7. INSERT into students_log VALUES (user(),
8. CONCAT('Update Student Record ', OLD.name, ' Previous Class :',
9. OLD.class, ' Present Class ', NEW.class));
10. END $$
11.
12. DELIMITER ;
 In this trigger, we have first specified the trigger name after_update_studentsInfo.
Then, specify the triggering event. Third, we have specified the table name on which the
trigger is associated. Finally, we have written the trigger logic inside the trigger body
that performs updation in the "students" table and keeps the log information in the
"students_log" table.

How to call the AFTER UPDATE trigger?

First, we will update the "students" table using the following statements that invoke the
above-created trigger:

1. mysql> UPDATE students SET class = class + 1;

Next, we will query data from the students and students_log table. We can see that
table has been updated after the execution of the query. See the below output:
Again, we will query data from the students_log table that keeps the current user id and
a description regarding the current update. See the below output:

How to create AFTER UPDATE trigger in MySQL

workbench?
To create an AFTER UPDATE trigger in workbench, we first launch the MySQL
Workbench and log in using the username and password. We will get the UI as follows:
Now do the following steps to create an AFTER UPDATE trigger:

1. Go to the Navigation tab and click on the Schema menu. It will display all databases
available in the MySQL database server.
2. Select the database (for example, mystudentdb). Then, double click on the selected
schema. It displays the sub-menu containing Tables, Views, Functions, and Stored
Procedures. See the below screen.

3. Expand the Tables sub-menu and select a table on which you want to create a trigger.
Then, right-click on the selected table (for example, students), and click on the Alter
Table option. See the below image:
4. Clicking on the Alter Table option gives the screen as below:
5. Now, click on the Trigger tab shown in the previous section's red rectangular box,
then select the Timing/Event AFTER UPDATE. We will notice that there is a (+) icon
button to add a trigger. Clicking on that button, we will get a default code on the
trigger based on choosing Timing/Event:
6. Now, complete the trigger code, review them once again, and if no error is found,
click on the Apply button.

7. After clicking on the Apply button, click on the Finish button to complete the
process.
8. If we look at the schema menu, we can see student_update_trigger under the
"students" table as follows:
 MySQL BEFORE DELETE Trigger
BEFORE DELETE Trigger in MySQL is invoked automatically whenever a delete operation
is fired on the table. In this article, we are going to learn how to create a before delete
trigger with its syntax and example.

Syntax
The following is the syntax to create a BEFORE DELETE trigger in MySQL:

1. CREATE TRIGGER trigger_name

2. BEFORE DELETE
3. ON table_name FOR EACH ROW
4. Trigger_body ;

The BEFORE DELETE trigger syntax parameter can be explained as below:

o First, we will specify the name of the trigger that we want to create. It should be
unique within the schema.
o Second, we will specify the trigger action time, which should be BEFORE DELETE.
This trigger will be invoked before each row of alterations occurs on the table.
o Third, we will specify the name of a table to which the trigger is associated. It
must be written after the ON keyword. If we did not specify the table name, a
trigger would not exist.
o Finally, we will specify the statement for execution when the trigger is activated.

If we want to execute multiple statements, we will use the BEGIN END block that
contains a set of queries to define the logic for the trigger. See the below syntax:

49.3M
905
HTML Tutorial

1. DELIMITER $$
2. CREATE TRIGGER trigger_name BEFORE DELETE
3. ON table_name FOR EACH ROW
4. BEGIN
5. variable declarations
6. trigger code
7. END$$
8. DELIMITER ;

Restrictions

o We can access the OLD rows but cannot update them in a BEFORE DELETE
trigger.
o We cannot access the NEW rows. It is because there are no new row exists.
o We cannot create a BEFORE DELETE trigger on a VIEW.

BEFORE DELETE Trigger Example

Let us understand how to create a BEFORE DELETE trigger using the CREATE TRIGGER
statement in MySQL with an example.

Suppose we have created a table named salaries to store the salary information of an
employee as follows:

1. CREATE TABLE salaries (

2. emp_num INT PRIMARY KEY,
3. valid_from DATE NOT NULL,
4. amount DEC(8 , 2 ) NOT NULL DEFAULT 0
5. );

Next, we will insert some records into this table using the below statement:

1. INSERT INTO salaries (emp_num, valid_from, amount)

2. VALUES
3. (102, '2020-01-10', 45000),
4. (103, '2020-01-10', 65000),
5. (105, '2020-01-10', 55000),
6. (107, '2020-01-10', 70000),
7. (109, '2020-01-10', 40000);

Execute the SELECT query to see the table data.

 Third, we will create another table named salary_archives that keeps the information of
deleted salary.

1. CREATE TABLE salary_archives (

2. id INT PRIMARY KEY AUTO_INCREMENT,
3. emp_num INT,
4. valid_from DATE NOT NULL,
5. amount DEC(18 , 2 ) NOT NULL DEFAULT 0,
6. deleted_time TIMESTAMP DEFAULT NOW()
7. );

We will then create a BEFORE DELETE trigger that inserts a new record into the
salary_archives table before a row is deleted from the salaries table.

1. DELIMITER $$
2.
3. CREATE TRIGGER before_delete_salaries
4. BEFORE DELETE
5. ON salaries FOR EACH ROW
6. BEGIN
7. INSERT INTO salary_archives (emp_num, valid_from, amount)
8. VALUES(OLD. emp_num, OLD.valid_from, OLD.amount);
9. END$$
10.
11. DELIMITER ;
 In this trigger, we have first specified the trigger name before_delete_salaries. Then,
specify the triggering event. Third, we have specified the table name on which the
trigger is associated. Finally, we have written the trigger logic inside the trigger body
that insert the deleted row into the salary_archives table.

How to call the BEFORE DELETE trigger?

Let us test the above created BEFORE DELETE trigger and how we can call them. So first,
we will remove a row from the salaries table:

1. mysql> DELETE FROM salaries WHERE emp_num = 105;

Second, we will query data from the salary_archives table to verify the above-created
trigger is invoked or not by using the select statement:

1. mysql> SELECT * FROM salary_archives;

After executing a statement, we can see that the trigger was invoked successfully and
inserted a new record into the salary_archives table.
 Third, we will remove all rows from the salaries table:

1. mysql> DELETE FROM salaries;

Finally, we will query data from the salary_archives table again. The trigger was called
four times because the DELETE statement removed four records from the salaries table.
See the below output:

How to create BEFORE DELETE Trigger in MySQL

workbench?
To create a BEFORE DELETE trigger using MySQL workbench, we first need to launch it
and then log in using the username and password we created earlier. We will get the
screen as follows:
Now do the following steps for creating BEFORE DELETE trigger:

1. Go to the Navigation tab and click on the Schema menu that contains all the
databases available in the MySQL server.

2. Select the database (for example, employeedb), double click on it. It will show
the sub-menu that contains Tables, Views, Functions, and Stored Procedures. See the
below screen.
3. Expand the Tables sub-menu and select the table on which you want to create
a trigger. After selecting a table, right-click on the selected table (for example, salaries),
and then click on the Alter Table option. See the below image:
4. Clicking on the Alter Table option gives the screen as below:

5. Now, click on the Trigger tab shown in the red rectangular box of the previous
section, then select the Timing/Event BEFORE DELETE. We will notice that there is a (+)
icon button to add a trigger. Clicking on that button, we will get a default code on
trigger based on choosing Timing/Event:
6. Now, complete the trigger code, review them once again, and if no error is found,
click on the Apply button.
7. After clicking on the Apply button, click on the Finish button for completion.
 8. If we take at the schema menu, we will see the trigger salaries_before_trigger under
the salaries table as follows:

MySQL AFTER DELETE Trigger

The AFTER DELETE Trigger in MySQL is invoked automatically whenever a delete event is
fired on the table. In this article, we are going to learn how to create an AFTER DELETE
trigger with its syntax and example.

Syntax
The following is the syntax to create an AFTER DELETE trigger in MySQL:

1. CREATE TRIGGER trigger_name

2. AFTER DELETE
3. ON table_name FOR EACH ROW
4. Trigger_body ;

The AFTER DELETE trigger syntax parameter can be explained as below:

 o First, we will specify the name of the trigger that we want to create. It should be
unique within the schema.
o Second, we will specify the trigger action time, which should be AFTER DELETE.
This trigger will be invoked after each row of alterations occurs on the table.
o Third, we will specify the name of a table to which the trigger is associated. It
must be written after the ON keyword. If we did not specify the table name, a
trigger would not exist.
o Finally, we will specify the trigger body that contains a statement for execution
when the trigger is activated.

If we want to execute multiple statements, we will use the BEGIN END block that
contains a set of SQL queries to define the logic for the trigger. See the below syntax:

58.1M
1.1K
C++ vs Java

1. DELIMITER $$
2. CREATE TRIGGER trigger_name AFTER DELETE
3. ON table_name FOR EACH ROW
4. BEGIN
5. variable declarations
6. trigger code
7. END$$
8. DELIMITER ;

Restrictions

o We can access the OLD rows but cannot update them in the AFTER DELETE
trigger.
o We cannot access the NEW rows. It is because there are no NEW row exists.
o We cannot create an AFTER DELETE trigger on a VIEW.

AFTER DELETE Trigger Example

Let us understand how to create an AFTER DELETE trigger using the CREATE TRIGGER
statement in MySQL with an example.
 Suppose we have created a table named salaries to store the salary information of an
employee as follows:

1. CREATE TABLE salaries (

2. emp_num INT PRIMARY KEY,
3. valid_from DATE NOT NULL,
4. amount DEC(8 , 2 ) NOT NULL DEFAULT 0
5. );

Next, we will insert some records into this table using the below statement:

1. INSERT INTO salaries (emp_num, valid_from, amount)

2. VALUES
3. (102, '2020-01-10', 45000),
4. (103, '2020-01-10', 65000),
5. (105, '2020-01-10', 55000),
6. (107, '2020-01-10', 70000),
7. (109, '2020-01-10', 40000);

Execute the SELECT query to see the table data.

Third, we will create another table named total_salary_budget that keeps the salary
information from the salaries table.

1. CREATE TABLE total_salary_budget(

2. total_budget DECIMAL(10,2) NOT NULL
3. );
 Fourth, we will use the SUM() function that returns the total salary from the salaries
table and keep this information in the total_salary_budget table:

1. mysql> INSERT INTO total_salary_budget (total_budget)

2. SELECT SUM(amount) FROM salaries;

Execute the SELECT statement to verify the table:

We will then create an AFTER DELETE trigger that updates the total salary into the
total_salary_budget table after a row is deleted from the salaries table.

1. DELIMITER $$
2.
3. CREATE TRIGGER after_delete_salaries
4. AFTER DELETE
5. ON salaries FOR EACH ROW
6. BEGIN
7. UPDATE total_salary_budget SET total_budget = total_budget - old.amount;
8. END$$
9.
10. DELIMITER ;
 In this trigger, we have first specified the trigger name after_delete_salaries. Then,
specify the triggering event. Third, we have specified the table name on which the
trigger is associated. Finally, we have written the trigger logic inside the trigger body
that updates the total salary into the total_salary_budget table after a row is deleted
from the salaries table.

How to call the AFTER DELETE trigger?

First, we will delete a salary from the salaries table using the following statements to
invoke the above-created trigger:

1. mysql> DELETE FROM salaries WHERE emp_num = 105;

Next, we will query data from the total_salary_budget table. We can see that table has
been modified after the execution of the query. See the below output:

1. mysql> SELECT * FROM total_salary_budget;

 In the output, we can see that the deleted salary reduces the total_budget.

Third, we will remove all data from the salaries table:

1. mysql> DELETE FROM salaries;

Again, we will query data from the total_salary_budget table. We can see that the trigger
updated the table to zero after the execution of the query. See the below output:

How to create AFTER DELETE Trigger in MySQL

workbench?
To create an after insert trigger using this tool, we first need to launch the MySQL
Workbench and log in using the username and password we have created earlier. We
will get the screen as follows:
Now do the following steps for creating an AFTER DELETE trigger:

1. Go to the Navigation tab and click on the Schema menu that contains all the
databases available in the MySQL server.

2. Select the database (for example, employeedb), double click on it that shows
the sub-menu containing Tables, Views, Functions, and Stored Procedures. See the
below screen.
3. Expand the Tables sub-menu and select the table on which you want to create a
trigger. After selecting a table, right-click on the selected table (for example, salaries),
and then click on the Alter Table option. See the below image:
4. Clicking on the Alter Table option gives the screen as below:
5. Now, click on the Trigger tab shown in the previous section's red rectangular box,
then select the Timing/Event AFTER DELETE. We will notice that there is a (+) icon
button to add a trigger. Clicking on that button, we will get a default code on the trigger
based on choosing Timing/Event:
6. Now, complete the trigger code, review them once again, and if no error is found,
click on the Apply button.

7. After clicking on the Apply button, click on the Finish button for completion.
8. If we look at the schema menu, we can see salaries_AFTER_DELETE trigger under
the salaries table as follows: