Why triggers are needed in SQL - See It in Action

Understanding Why Triggers Are Needed in SQL

📖 Scenario: You are managing a small online bookstore database. You want to keep track of every time a book's price changes so you can analyze pricing trends later.

🎯 Goal: Build a simple SQL trigger that automatically records price changes in a separate table whenever the price of a book is updated.

📋 What You'll Learn

Create a table called books with columns book_id, title, and price

Create a table called price_changes with columns change_id, book_id, old_price, new_price, and change_date

Create a trigger called log_price_change that fires after an update on books

The trigger should insert a record into price_changes only if the price has changed

💡 Why This Matters

🌍 Real World

In real businesses, triggers help keep audit logs, enforce rules, and automate updates without extra application code.

💼 Career

Database administrators and developers use triggers to maintain data integrity and automate workflows in many industries.

1

Create the books table

Create a table called books with columns book_id as an integer primary key, title as text, and price as a decimal number.

SQL

-- Create the books table
-- Your code here

Hint

Use CREATE TABLE with the specified columns and types.

2

Create the price_changes table

Create a table called price_changes with columns change_id as an auto-increment integer primary key, book_id as integer, old_price and new_price as decimal numbers, and change_date as a timestamp.

SQL

CREATE TABLE books (
    book_id INT PRIMARY KEY,
    title TEXT,
    price DECIMAL(10, 2)
);
-- Create the price_changes table
-- Your code here

Hint

Use SERIAL for auto-incrementing change_id and set default for change_date.

3

Create the trigger function to log price changes

Create a trigger function called log_price_change_func that inserts a record into price_changes with the book_id, old_price, new_price, and current timestamp, but only if the price has changed.

SQL

CREATE TABLE books (
    book_id INT PRIMARY KEY,
    title TEXT,
    price DECIMAL(10, 2)
);

CREATE TABLE price_changes (
    change_id SERIAL PRIMARY KEY,
    book_id INT,
    old_price DECIMAL(10, 2),
    new_price DECIMAL(10, 2),
    change_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

-- Create the trigger function
-- Your code here

Hint

Use a trigger function with IF to check price change and insert accordingly.

4

Create the trigger to call the function after update

Create a trigger called log_price_change that fires AFTER UPDATE on the books table and calls the log_price_change_func function.

SQL

CREATE TABLE books (
    book_id INT PRIMARY KEY,
    title TEXT,
    price DECIMAL(10, 2)
);

CREATE TABLE price_changes (
    change_id SERIAL PRIMARY KEY,
    book_id INT,
    old_price DECIMAL(10, 2),
    new_price DECIMAL(10, 2),
    change_date TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);

CREATE OR REPLACE FUNCTION log_price_change_func() RETURNS TRIGGER AS $$
BEGIN
    IF NEW.price  OLD.price THEN
        INSERT INTO price_changes(book_id, old_price, new_price, change_date)
        VALUES (NEW.book_id, OLD.price, NEW.price, CURRENT_TIMESTAMP);
    END IF;
    RETURN NEW;
END;
$$ LANGUAGE plpgsql;

-- Create the trigger
-- Your code here

Hint

Use CREATE TRIGGER with AFTER UPDATE and FOR EACH ROW.

Practice

1. Why are triggers needed in a database?
Triggers are special procedures that run automatically. What is their main purpose?

easy

A. To write complex queries for reports

B. To manually update data in tables

C. To create new tables in the database

D. To automatically perform actions when data changes happen

Solution

1. Step 1: Understand what triggers do

   Triggers run automatically when data changes happen in a table, like insert, update, or delete.

2. Step 2: Identify the main purpose

   The main purpose is to automate actions without manual intervention, such as enforcing rules or logging changes.

3. Final Answer:

   To automatically perform actions when data changes happen -> Option D

4. Quick Check:

   Triggers run automatically = D [OK]

Hint: Triggers act automatically on data changes [OK]

Common Mistakes:

• Thinking triggers are for manual updates
• Confusing triggers with creating tables
• Assuming triggers write reports

2. Which of the following is the correct syntax to create a trigger that runs after an INSERT on a table named Employees?

easy

A. CREATE TRIGGER trg AFTER INSERT ON Employees BEGIN ... END;

B. CREATE TRIGGER trg BEFORE UPDATE ON Employees BEGIN ... END;

C. CREATE TRIGGER trg ON Employees AFTER DELETE BEGIN ... END;

D. CREATE TRIGGER trg INSERT AFTER Employees BEGIN ... END;

Solution

1. Step 1: Identify correct trigger timing and event

   The question asks for a trigger after INSERT on Employees, so syntax must say AFTER INSERT ON Employees.

2. Step 2: Check syntax structure

   CREATE TRIGGER trg AFTER INSERT ON Employees BEGIN ... END; matches the correct order: CREATE TRIGGER name AFTER INSERT ON table BEGIN ... END;

3. Final Answer:

   CREATE TRIGGER trg AFTER INSERT ON Employees BEGIN ... END; -> Option A

4. Quick Check:

   Correct trigger syntax = C [OK]

Hint: Syntax: CREATE TRIGGER name AFTER|BEFORE event ON table [OK]

Common Mistakes:

• Mixing BEFORE and AFTER keywords
• Placing table name in wrong position
• Using ON before event instead of after

3. Consider this trigger on table Orders:

CREATE TRIGGER trg_log AFTER UPDATE ON Orders BEGIN INSERT INTO AuditLog VALUES('Order updated'); END;

What happens when an order is updated?

medium

A. Nothing happens automatically

B. A new row with 'Order updated' is added to AuditLog

C. The Orders table is deleted

D. The update on Orders is canceled

Solution

1. Step 1: Understand trigger action on UPDATE

   The trigger runs AFTER UPDATE on Orders and inserts a row into AuditLog with text 'Order updated'.

2. Step 2: Identify the effect of the trigger

   Each time an order is updated, a new row is added to AuditLog recording the event.

3. Final Answer:

   A new row with 'Order updated' is added to AuditLog -> Option B

4. Quick Check:

   Trigger inserts log row = B [OK]

Hint: Trigger inserts log row after update [OK]

Common Mistakes:

• Thinking trigger cancels update
• Assuming no action happens automatically
• Confusing trigger with delete operation

4. You wrote this trigger:

CREATE TRIGGER trg_check BEFORE INSERT ON Users BEGIN IF NEW.age < 18 THEN SIGNAL SQLSTATE '45000' SET MESSAGE_TEXT = 'Age must be 18 or older'; END IF; END;

But it does not prevent inserting users younger than 18. What is the likely error?

medium

A. The trigger does not have a proper delimiter for multiple statements

B. The SIGNAL statement syntax is incorrect

C. The trigger should be AFTER INSERT, not BEFORE

D. Triggers cannot check conditions on NEW data

Solution

1. Step 1: Analyze trigger structure with multiple statements

   The trigger has IF and SIGNAL inside BEGIN...END, which requires proper statement delimiters (like semicolons) to separate commands.

2. Step 2: Identify missing delimiter issue

   Without delimiters, the database cannot parse the trigger body correctly, so the condition check fails.

3. Final Answer:

   The trigger does not have a proper delimiter for multiple statements -> Option A

4. Quick Check:

   Missing delimiters cause trigger failure = A [OK]

Hint: Use delimiters for multiple statements in triggers [OK]

Common Mistakes:

• Changing BEFORE to AFTER incorrectly
• Assuming SIGNAL syntax is wrong without checking
• Believing triggers can't access NEW data

5. A company wants to ensure that whenever a product's price is updated, the old price is saved in a PriceHistory table automatically. Which trigger design best achieves this?

hard

A. A BEFORE DELETE trigger on Products that inserts old price into PriceHistory

B. An AFTER INSERT trigger on Products that inserts new price into PriceHistory

C. An AFTER UPDATE trigger on Products that inserts old price into PriceHistory

D. A BEFORE UPDATE trigger on Products that inserts old price into PriceHistory

Solution

1. Step 1: Understand when old price is available

   The old price is available after the update operation starts but before the new data replaces it, so a trigger on UPDATE is needed.

2. Step 2: Choose trigger timing to save old price

   Using AFTER UPDATE ensures the update succeeded, and the trigger can insert the old price (accessible via OLD) into PriceHistory.

3. Final Answer:

   An AFTER UPDATE trigger on Products that inserts old price into PriceHistory -> Option C

4. Quick Check:

   Save old price after update = A [OK]

Hint: Use AFTER UPDATE trigger to save old data changes [OK]

Common Mistakes:

• Using BEFORE DELETE instead of UPDATE
• Using AFTER INSERT which doesn't track price changes
• Choosing BEFORE UPDATE which may block or cause errors