Trigger best practices and limitations in MySQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a database trigger?

A database trigger is a special procedure that automatically runs when certain events happen in the database, like inserting, updating, or deleting data.

beginner

Why should triggers be kept simple and fast?

Because triggers run automatically during data changes, slow or complex triggers can delay the main operation and affect database performance.

intermediate

Name one limitation of MySQL triggers.

MySQL allows only one trigger per table for each combination of timing (BEFORE/AFTER) and event (INSERT/UPDATE/DELETE), which limits splitting complex logic across multiple triggers.

intermediate

What is a common best practice when using triggers to avoid unexpected behavior?

Avoid having triggers that cause other triggers to fire in a loop, which can cause infinite recursion and crash the database.

beginner

How can you test a trigger safely before applying it in production?

Test triggers in a development or staging environment with sample data to ensure they work correctly and do not cause errors or performance issues.

Which event can a MySQL trigger NOT respond to?

A INSERT

B UPDATE

C DELETE

D SELECT

Triggers in MySQL cannot be set to run on SELECT statements; they only respond to data changes like INSERT, UPDATE, or DELETE.

What happens if a trigger causes another trigger to fire repeatedly in MySQL?

A The database optimizes and stops the loop automatically

B It can cause infinite recursion and crash the database

C Triggers do not fire other triggers in MySQL

D The second trigger runs only once

If triggers call each other repeatedly without stopping, it causes infinite recursion which can crash the database.

Which is a good practice when writing triggers?

A Keep triggers simple and fast

B Avoid testing triggers

C Use triggers to replace all application logic

D Make triggers as complex as possible

Keeping triggers simple and fast helps maintain good database performance and avoids delays.

Can MySQL triggers call stored procedures that modify data?

A Yes, always

B No, this is not allowed

C Only if the procedure is read-only

D Only in MySQL 8.0 and above

Yes, MySQL triggers can call stored procedures that modify data, but this must be done carefully to avoid recursion issues.

Where should you test triggers before using them in production?

A Directly on the live database

B Only on backups

C On a development or staging environment

D No testing is needed

Testing triggers in a development or staging environment helps catch errors and performance issues before affecting live data.

Explain the best practices to follow when creating triggers in MySQL.

Think about performance, safety, and testing.

Describe the main limitations of MySQL triggers.

Focus on what triggers cannot do and what risks they have.

Practice

1. Which of the following is a best practice when creating MySQL triggers?

easy

A. Keep trigger logic simple to avoid performance issues.

B. Use triggers to replace all application logic.

C. Allow triggers to call themselves recursively without limits.

D. Write triggers that perform complex calculations on large datasets.

Solution

1. Step 1: Understand trigger performance impact

   Triggers run automatically on data changes, so complex logic can slow down database operations.

2. Step 2: Identify best practice for trigger design

   Keeping trigger logic simple helps maintain good performance and avoids unexpected delays.

3. Final Answer:

   Keep trigger logic simple to avoid performance issues. -> Option A

4. Quick Check:

   Simple trigger logic = Better performance [OK]

Hint: Keep triggers simple to avoid slowdowns [OK]

Common Mistakes:

• Trying to put all business logic inside triggers
• Allowing infinite recursion in triggers
• Using triggers for heavy data processing

2. Which syntax correctly defines a BEFORE INSERT trigger in MySQL?

easy

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

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

C. CREATE TRIGGER trg BEFORE UPDATE ON table_name FOR EACH ROW BEGIN ... END;

D. CREATE TRIGGER trg BEFORE DELETE ON table_name FOR EACH ROW BEGIN ... END;

Solution

1. Step 1: Identify trigger timing and event

   BEFORE INSERT triggers run before a new row is inserted.

2. Step 2: Match syntax to BEFORE INSERT event

   CREATE TRIGGER trg BEFORE INSERT ON table_name FOR EACH ROW BEGIN ... END; uses BEFORE INSERT, correct timing and event for this trigger.

3. Final Answer:

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

4. Quick Check:

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

Hint: BEFORE triggers run before data changes [OK]

Common Mistakes:

• Confusing BEFORE and AFTER keywords
• Using wrong event like UPDATE or DELETE
• Missing FOR EACH ROW clause

3. Given this trigger, what happens when a new row is inserted?

CREATE TRIGGER trg BEFORE INSERT ON employees FOR EACH ROW BEGIN SET NEW.salary = NEW.salary * 1.1; END;

medium

A. The trigger causes a syntax error.

B. The salary is increased by 10% before insertion.

C. The salary remains unchanged.

D. The insertion fails due to recursion.

Solution

1. Step 1: Analyze trigger action on BEFORE INSERT

   The trigger modifies the NEW.salary value by multiplying it by 1.1 before the row is inserted.

2. Step 2: Understand effect on inserted data

   The inserted row will have salary increased by 10% automatically.

3. Final Answer:

   The salary is increased by 10% before insertion. -> Option B

4. Quick Check:

   BEFORE INSERT modifies NEW.salary = increased salary [OK]

Hint: BEFORE triggers can modify NEW row data [OK]

Common Mistakes:

• Thinking triggers run after insertion
• Assuming salary stays the same
• Confusing NEW and OLD keywords

4. What is wrong with this trigger definition?

CREATE TRIGGER trg AFTER UPDATE ON employees FOR EACH ROW BEGIN UPDATE employees SET salary = salary * 1.05 WHERE id = NEW.id; END;

medium

A. It will not update any rows because NEW.id is invalid.

B. Syntax error due to missing DELIMITER statement.

C. Triggers cannot use UPDATE statements inside their body.

D. It causes infinite recursion by updating the same table inside the trigger.

Solution

1. Step 1: Identify trigger action on AFTER UPDATE

   The trigger updates the same table employees inside an AFTER UPDATE trigger.

2. Step 2: Understand recursion risk

   Updating the same table inside its own UPDATE trigger causes the trigger to call itself repeatedly, causing infinite recursion.

3. Final Answer:

   It causes infinite recursion by updating the same table inside the trigger. -> Option D

4. Quick Check:

   Trigger updating same table = recursion risk [OK]

Hint: Avoid updating same table inside its trigger [OK]

Common Mistakes:

• Ignoring recursion risk
• Assuming syntax error without DELIMITER
• Thinking triggers can't run UPDATE statements

5. You want to log every DELETE action on the orders table without slowing down the delete operation. Which trigger design is best?

hard

A. Use a BEFORE DELETE trigger that updates the orders table with a log message.

B. Use an AFTER DELETE trigger that updates the orders table itself.

C. Use an AFTER DELETE trigger that inserts a log record into a separate table.

D. Use a BEFORE DELETE trigger that performs complex calculations before deleting.

Solution

1. Step 1: Choose trigger timing for logging

   AFTER DELETE triggers run after the row is deleted, so they don't block the delete operation.

2. Step 2: Select action that avoids slowing delete

   Inserting a log record into a separate table is efficient and safe, avoiding recursion or delays.

3. Final Answer:

   Use an AFTER DELETE trigger that inserts a log record into a separate table. -> Option C

4. Quick Check:

   AFTER DELETE + separate log table = best practice [OK]

Hint: Log deletes AFTER action to avoid delays [OK]

Common Mistakes:

• Updating same table inside trigger causing recursion
• Using BEFORE DELETE for logging causing delays
• Doing heavy calculations inside triggers