AFTER INSERT triggers in MySQL - Time & Space Complexity

Time Complexity: AFTER INSERT triggers

O(n)

Understanding Time Complexity

When using AFTER INSERT triggers in MySQL, it's important to understand how the time to run your database operations changes as you add more data.

We want to know how the trigger affects the total work the database does when new rows are inserted.

Scenario Under Consideration

Analyze the time complexity of the following AFTER INSERT trigger.

CREATE TRIGGER after_insert_example
AFTER INSERT ON orders
FOR EACH ROW
BEGIN
  INSERT INTO audit_log(order_id, action_time) VALUES (NEW.id, NOW());
END;
    

This trigger adds a record to an audit_log table every time a new order is inserted.

Identify Repeating Operations

Let's find the repeating parts in this trigger.

• Primary operation: The trigger runs an INSERT into audit_log for each new row inserted into orders.
• How many times: Once per inserted row, because the trigger is FOR EACH ROW.

How Execution Grows With Input

As you insert more rows, the trigger runs once for each row.

Input Size (n)	Approx. Operations
10	10 inserts into audit_log
100	100 inserts into audit_log
1000	1000 inserts into audit_log

Pattern observation: The work grows directly with the number of inserted rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to complete the inserts and trigger actions grows linearly with the number of rows inserted.

Common Mistake

[X] Wrong: "The trigger runs only once no matter how many rows are inserted."

[OK] Correct: In MySQL, AFTER INSERT triggers defined FOR EACH ROW run once per inserted row, so the work adds up with more rows.

Interview Connect

Understanding how triggers add work helps you design efficient databases and explain your choices clearly in conversations.

Self-Check

What if the trigger was defined FOR EACH STATEMENT instead of FOR EACH ROW? How would the time complexity change?

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