Database triggers for automation in Supabase - Step-by-Step Execution

Process Flow - Database triggers for automation

Event occurs in database

↓

Trigger detects event

↓

Trigger runs defined function

↓

Function performs automation task

↓

Database state or external action updated

When a specific event happens in the database, a trigger detects it and runs a function that automates a task, updating the database or performing other actions.

Execution Sample

Supabase

CREATE TRIGGER notify_insert
AFTER INSERT ON messages
FOR EACH ROW
EXECUTE FUNCTION notify_new_message();

This trigger runs the function notify_new_message() every time a new row is inserted into the messages table.

Process Table

Step	Event	Trigger Action	Function Called	Effect
1	New row inserted into messages	Trigger notify_insert fires	notify_new_message()	Sends notification about new message
2	Function completes	No further triggers	None	Notification sent, database unchanged
3	Waiting for next event	Idle	None	System ready for next insert

💡 No new insert event, so trigger does not fire and automation pauses

Status Tracker

Variable	Start	After Step 1	After Step 2	Final
messages table rows	N	N+1	N+1	N+1
notifications sent	0	1	1	1

Key Moments - 3 Insights

Why does the trigger only run after an insert event?

Because the trigger is defined with AFTER INSERT ON messages, it only activates when a new row is added, as shown in execution_table step 1.

Does the trigger run if no new row is inserted?

No, the trigger waits for the insert event. Without it, the trigger does not fire, as explained in the exit_note.

Can the function called by the trigger change the database?

Yes, the function can update the database or perform other actions. In this example, it sends a notification but does not change the database further (execution_table step 2).

Visual Quiz - 3 Questions

Look at the execution_table, what happens at step 1?

A Trigger waits for an update event

B Function sends notification before insert

C Trigger fires and function runs after a new row is inserted

D No action occurs

💡 Hint

See execution_table row 1 describing the trigger firing after insert

According to variable_tracker, how many notifications are sent after step 2?

A 0

B 1

C N

D N+1

💡 Hint

Check notifications sent variable after step 2 in variable_tracker

If the trigger was changed to AFTER UPDATE, when would it fire?

A When a row is updated

B When a new row is inserted

C When a row is deleted

D Never

💡 Hint

Triggers fire on the event they are defined for, see concept_flow

Concept Snapshot

Database triggers run automatically when specific events happen.
Define triggers for INSERT, UPDATE, or DELETE events.
Triggers call functions to automate tasks like notifications.
They help keep data and actions in sync without manual steps.
In Supabase, use CREATE TRIGGER with EXECUTE FUNCTION syntax.

Full Transcript

Database triggers automate tasks by running functions when events happen in the database. For example, when a new message is inserted into the messages table, a trigger detects this insert event and runs a function to send a notification. The trigger is defined to run after insert events only, so it does not activate on updates or deletes. The function can perform actions like sending notifications or updating other tables. This automation helps keep the system responsive without manual intervention. The execution table shows the trigger firing after a new row is added, the function running, and the system waiting for the next event. Variables like the number of messages and notifications sent update accordingly. Understanding when triggers fire and what functions do is key to using database automation effectively.

Practice

1. What is the main purpose of a database trigger in Supabase?

easy

A. To manually update data in the database

B. To automatically run a function when data changes in a table

C. To create a backup of the database

D. To increase the database storage size

Solution

1. Step 1: Understand what triggers do

   Triggers run automatically when data changes like insert, update, or delete.

2. Step 2: Identify the purpose in Supabase

   Supabase triggers automate running functions on data changes without manual intervention.

3. Final Answer:

   To automatically run a function when data changes in a table -> Option B

4. Quick Check:

   Trigger = auto-run function on data change [OK]

Hint: Triggers run code automatically on data changes [OK]

Common Mistakes:

• Thinking triggers require manual activation
• Confusing triggers with backups
• Assuming triggers increase storage

2. Which of the following is the correct syntax to create a trigger in Supabase SQL?

easy

A. CREATE TRIGGER trigger_name WHEN INSERT ON table_name EXECUTE function_name();

B. CREATE TRIGGER trigger_name BEFORE UPDATE table_name CALL function_name();

C. CREATE TRIGGER trigger_name ON table_name AFTER DELETE RUN function_name();

D. CREATE TRIGGER trigger_name AFTER INSERT ON table_name EXECUTE FUNCTION function_name();

Solution

1. Step 1: Recall correct trigger syntax in PostgreSQL (used by Supabase)

   The correct syntax uses CREATE TRIGGER, timing (AFTER/BEFORE), event (INSERT/UPDATE/DELETE), ON table, and EXECUTE FUNCTION.

2. Step 2: Match options to syntax

   CREATE TRIGGER trigger_name AFTER INSERT ON table_name EXECUTE FUNCTION function_name(); matches the correct syntax: CREATE TRIGGER name AFTER INSERT ON table EXECUTE FUNCTION func(); others use wrong keywords like CALL, RUN, or WHEN.

3. Final Answer:

   CREATE TRIGGER trigger_name AFTER INSERT ON table_name EXECUTE FUNCTION function_name(); -> Option D

4. Quick Check:

   CREATE TRIGGER ... EXECUTE FUNCTION ... [OK]

Hint: Use EXECUTE FUNCTION, not CALL or RUN in triggers [OK]

Common Mistakes:

• Using CALL or RUN instead of EXECUTE FUNCTION
• Missing ON keyword before table name
• Using WHEN instead of BEFORE or AFTER

3. Given this trigger function in Supabase SQL:

CREATE FUNCTION log_insert() RETURNS trigger AS $$ BEGIN INSERT INTO logs(table_name, action) VALUES (TG_TABLE_NAME, 'insert'); RETURN NEW; END; $$ LANGUAGE plpgsql;

And this trigger:

CREATE TRIGGER after_insert_log AFTER INSERT ON users EXECUTE FUNCTION log_insert();

What happens when a new row is inserted into the users table?

medium

A. A new row is added to the logs table recording the insert action on users

B. The insert into users is blocked and logs table is updated

C. Nothing happens because the trigger is AFTER INSERT

D. The users table row is deleted after insert

Solution

1. Step 1: Understand the trigger function behavior

   The function inserts a row into logs with the table name and action 'insert' whenever triggered.

2. Step 2: Understand the trigger timing and event

   The trigger runs AFTER INSERT on users, so after a new user row is added, the function runs and logs the action.

3. Final Answer:

   A new row is added to the logs table recording the insert action on users -> Option A

4. Quick Check:

   AFTER INSERT triggers log insert action [OK]

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

Common Mistakes:

• Thinking AFTER INSERT blocks the insert
• Assuming trigger does nothing
• Confusing trigger timing with BEFORE

4. You wrote this trigger function:

CREATE FUNCTION update_timestamp() RETURNS trigger AS $$ BEGIN NEW.updated_at = NOW(); RETURN NEW; END; $$ LANGUAGE plpgsql;

And this trigger:

CREATE TRIGGER update_time BEFORE UPDATE ON orders EXECUTE FUNCTION update_timestamp();

But the updated_at column is not changing on updates. What is the likely problem?

medium

A. The trigger is AFTER UPDATE instead of BEFORE UPDATE

B. The trigger function is missing RETURN OLD

C. The trigger function does not modify NEW row correctly

D. The trigger function is not marked as VOLATILE

Solution

1. Step 1: Check how NEW row is modified in trigger

   The function sets NEW.updated_at = NOW() but does not assign it back properly; in PL/pgSQL, you must assign NEW.updated_at and then RETURN NEW.

2. Step 2: Confirm trigger timing and return

   The trigger is BEFORE UPDATE and returns NEW, which is correct. The problem is likely the function does not properly update the NEW record.

3. Final Answer:

   The trigger function does not modify NEW row correctly -> Option C

4. Quick Check:

   Modify NEW row correctly in BEFORE UPDATE triggers [OK]

Hint: Always RETURN NEW after modifying it in BEFORE UPDATE triggers [OK]

Common Mistakes:

• Not returning NEW after changes
• Using AFTER UPDATE instead of BEFORE UPDATE
• Returning OLD instead of NEW

5. You want to automatically archive deleted rows from the products table into products_archive using a trigger. Which approach correctly achieves this in Supabase?

hard

A. Create an AFTER DELETE trigger on products that inserts OLD row into products_archive

B. Create a BEFORE DELETE trigger on products that deletes from products_archive

C. Create an AFTER INSERT trigger on products_archive that copies rows to products

D. Create a BEFORE UPDATE trigger on products that moves rows to products_archive

Solution

1. Step 1: Understand the goal

   You want to save deleted rows from products into products_archive automatically.

2. Step 2: Choose correct trigger timing and action

   AFTER DELETE trigger on products can access OLD row data and insert it into products_archive. BEFORE DELETE is too early to archive after deletion. Other options do not archive deleted rows.

3. Final Answer:

   Create an AFTER DELETE trigger on products that inserts OLD row into products_archive -> Option A

4. Quick Check:

   AFTER DELETE triggers archive OLD row [OK]

Hint: Use AFTER DELETE triggers to archive deleted rows [OK]

Common Mistakes:

• Using BEFORE DELETE to archive after deletion
• Confusing insert and delete triggers
• Trying to archive on update instead of delete