AFTER INSERT triggers in MySQL

Introduction

AFTER INSERT triggers run automatically after new data is added to a table. They help you do extra tasks right after inserting data.

You want to log every new record added to a table.

You need to update related tables after adding new data.

You want to send notifications or alerts after data insertion.

You want to enforce additional rules or calculations after insert.

You want to keep an audit trail of changes in your database.

Syntax

MySQL

CREATE TRIGGER trigger_name
AFTER INSERT ON table_name
FOR EACH ROW
BEGIN
  -- statements to execute
END;

The trigger runs once for each row inserted.

Use NEW.column_name to access the inserted row's data.

Examples

This trigger adds a log entry every time a new user is added.

MySQL

CREATE TRIGGER log_new_user
AFTER INSERT ON users
FOR EACH ROW
BEGIN
  INSERT INTO user_log(user_id, action) VALUES (NEW.id, 'inserted');
END;

This trigger updates a stats table to count total orders after each new order.

MySQL

CREATE TRIGGER update_stats_after_insert
AFTER INSERT ON orders
FOR EACH ROW
BEGIN
  UPDATE stats SET total_orders = total_orders + 1;
END;

Sample Program

This example creates a products table and a product_log table. The trigger adds a log entry every time a new product is inserted.

MySQL

CREATE TABLE products (
  id INT AUTO_INCREMENT PRIMARY KEY,
  name VARCHAR(50),
  price DECIMAL(10,2)
);

CREATE TABLE product_log (
  log_id INT AUTO_INCREMENT PRIMARY KEY,
  product_id INT,
  action VARCHAR(20),
  log_time TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

DELIMITER $$
CREATE TRIGGER after_product_insert
AFTER INSERT ON products
FOR EACH ROW
BEGIN
  INSERT INTO product_log(product_id, action) VALUES (NEW.id, 'inserted');
END$$
DELIMITER ;

INSERT INTO products(name, price) VALUES ('Pen', 1.20);

SELECT * FROM product_log;

Important Notes

Remember to change the delimiter when creating triggers in MySQL to avoid errors.

AFTER INSERT triggers cannot modify the row being inserted, only act after insertion.

Summary

AFTER INSERT triggers run after new rows are added.

They help automate tasks like logging or updating related data.

Use NEW to access inserted row data inside the trigger.

Practice

1. What does an AFTER INSERT trigger do in MySQL?

easy

A. It deletes rows after insertion.

B. It runs before a row is inserted into a table.

C. It runs automatically after a new row is added to a table.

D. It prevents rows from being inserted.

Solution

1. Step 1: Understand trigger timing

   An AFTER INSERT trigger runs after a new row is successfully inserted into a table.

2. Step 2: Identify trigger purpose

   This trigger is used to perform actions like logging or updating related tables after insertion.

3. Final Answer:

   It runs automatically after a new row is added to a table. -> Option C

4. Quick Check:

   AFTER INSERT trigger = runs after insert [OK]

Hint: AFTER INSERT triggers run only after data is added [OK]

Common Mistakes:

• Confusing AFTER with BEFORE triggers
• Thinking triggers delete or block inserts
• Assuming triggers run before insertion

2. Which of the following is the correct syntax to create an AFTER INSERT trigger in MySQL?

easy

A. CREATE TRIGGER trg AFTER UPDATE ON table_name FOR EACH ROW BEGIN ... END;

B. CREATE TRIGGER trg BEFORE INSERT ON table_name FOR EACH ROW BEGIN ... END;

C. CREATE TRIGGER trg AFTER DELETE ON table_name FOR EACH ROW BEGIN ... END;

D. CREATE TRIGGER trg AFTER INSERT ON table_name FOR EACH ROW BEGIN ... END;

Solution

1. Step 1: Identify trigger timing and event

   The question asks for an AFTER INSERT trigger, so the syntax must include AFTER INSERT.

2. Step 2: Match syntax structure

   The correct syntax is CREATE TRIGGER trg AFTER INSERT ON table_name FOR EACH ROW BEGIN ... END;.

3. Final Answer:

   CREATE TRIGGER trg AFTER INSERT ON table_name FOR EACH ROW BEGIN ... END; -> Option D

4. Quick Check:

   AFTER INSERT trigger syntax = CREATE TRIGGER trg AFTER INSERT ON table_name FOR EACH ROW BEGIN ... END; [OK]

Hint: AFTER INSERT triggers use 'AFTER INSERT' in syntax [OK]

Common Mistakes:

• Using BEFORE instead of AFTER
• Using wrong event like UPDATE or DELETE
• Omitting FOR EACH ROW clause

3. Given this trigger and table:

CREATE TABLE users (id INT, name VARCHAR(20));
CREATE TABLE logs (msg VARCHAR(50));
DELIMITER $$
CREATE TRIGGER after_user_insert AFTER INSERT ON users
FOR EACH ROW BEGIN
  INSERT INTO logs VALUES (CONCAT('User ', NEW.name, ' added'));
END$$
DELIMITER ;

INSERT INTO users VALUES (1, 'Alice');
SELECT * FROM logs;

What will the SELECT query return?

medium

A. [{"msg": "User Alice added"}]

B. [{"msg": "User 1 added"}]

C. Empty result set

D. Syntax error

Solution

1. Step 1: Understand trigger action on insert

   The trigger inserts a log message using NEW.name after a user is added.

2. Step 2: Check inserted data and log content

   Inserting (1, 'Alice') triggers log insertion with message 'User Alice added'.

3. Final Answer:

   [{"msg": "User Alice added"}] -> Option A

4. Quick Check:

   NEW.name = 'Alice' logged [OK]

Hint: NEW accesses inserted row data inside AFTER INSERT [OK]

Common Mistakes:

• Using NEW.id instead of NEW.name for message
• Expecting no logs created
• Confusing syntax causing errors

4. You wrote this trigger but get an error:

CREATE TRIGGER trg AFTER INSERT ON users
FOR EACH ROW
INSERT INTO logs VALUES ('New user added');
INSERT INTO logs VALUES ('Trigger fired');

What is the problem?

medium

A. Missing BEGIN and END block for multiple statements

B. AFTER INSERT triggers cannot insert into other tables

C. FOR EACH ROW is not allowed in AFTER triggers

D. Trigger name cannot be 'trg'

Solution

1. Step 1: Check trigger body syntax

   When a trigger has more than one statement or uses procedural code, it needs BEGIN ... END block.

2. Step 2: Identify missing block

   The trigger has multiple statements but lacks BEGIN ... END, which is required for clarity and to avoid errors.

3. Final Answer:

   Missing BEGIN and END block for multiple statements -> Option A

4. Quick Check:

   Triggers need BEGIN...END for statements [OK]

Hint: Always use BEGIN...END for trigger statements [OK]

Common Mistakes:

• Assuming single statement triggers don't need BEGIN...END
• Thinking AFTER triggers can't modify other tables
• Misunderstanding FOR EACH ROW usage

5. You want to create an AFTER INSERT trigger on a sales table that updates a summary table with the total sales amount. Which approach is correct?

hard

A. Use OLD.amount in the trigger to subtract from the summary table's total.

B. Use NEW.amount in the trigger to add to the summary table's total after each insert.

C. Use a BEFORE INSERT trigger to update the summary table before inserting sales.

D. Use a DELETE trigger to update the summary table after sales are removed.

Solution

1. Step 1: Identify correct trigger timing for updating after insert

   AFTER INSERT triggers run after new rows are added, so they can safely update summary data using inserted values.

2. Step 2: Use NEW to access inserted row data

   Inside the trigger, NEW.amount gives the inserted sale amount to add to the summary.

3. Final Answer:

   Use NEW.amount in the trigger to add to the summary table's total after each insert. -> Option B

4. Quick Check:

   AFTER INSERT + NEW = update summary correctly [OK]

Hint: Use NEW in AFTER INSERT to access inserted data [OK]

Common Mistakes:

• Using OLD in INSERT triggers (OLD is NULL)
• Using BEFORE INSERT instead of AFTER INSERT
• Using DELETE triggers for insert updates