Row-level vs statement-level triggers in PostgreSQL - Interactive Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a row-level trigger that fires for each row inserted.

PostgreSQL

CREATE TRIGGER trg_example
AFTER INSERT ON employees
FOR EACH [1]
EXECUTE FUNCTION log_employee_insert();

Drag options to blanks, or click blank then click option'

AEVENT

BSTATEMENT

CTABLE

DROW

Attempts:

3 left

💡 Hint

Common Mistakes

Using FOR EACH STATEMENT instead of FOR EACH ROW for row-level triggers.

The FOR EACH ROW clause makes the trigger fire once for every row affected.

2fill in blank

medium

Complete the code to create a statement-level trigger that fires once per statement.

PostgreSQL

CREATE TRIGGER trg_example
BEFORE UPDATE ON orders
FOR EACH [1]
EXECUTE FUNCTION check_order_status();

Drag options to blanks, or click blank then click option'

ASTATEMENT

BTRANSACTION

CORDER

DROW

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing row-level and statement-level triggers.

The FOR EACH STATEMENT clause makes the trigger fire once per SQL statement.

3fill in blank

hard

Fix the error in the trigger creation by choosing the correct timing keyword.

PostgreSQL

CREATE TRIGGER trg_update
[1] UPDATE ON products
FOR EACH ROW
EXECUTE FUNCTION update_timestamp();

Drag options to blanks, or click blank then click option'

ADURING

BAFTER

CBEFORE

DON

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid timing keywords like DURING.

Triggers must use BEFORE or AFTER to specify timing. DURING is invalid.

4fill in blank

hard

Fill both blanks to create a trigger that fires once per statement before delete.

PostgreSQL

CREATE TRIGGER trg_cleanup
[1] DELETE ON sessions
FOR EACH [2]
EXECUTE FUNCTION cleanup_sessions();

Drag options to blanks, or click blank then click option'

ABEFORE

BROW

CSTATEMENT

DAFTER

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing row-level and statement-level keywords.

The trigger fires BEFORE the delete statement and once per STATEMENT.

5fill in blank

hard

Fill all three blanks to create a row-level trigger that fires after insert.

PostgreSQL

CREATE TRIGGER trg_audit
[1] [2] ON employees
FOR EACH [3]
EXECUTE FUNCTION audit_changes();

Drag options to blanks, or click blank then click option'

AAFTER

BINSERT

CROW

DBEFORE

Attempts:

3 left

💡 Hint

Common Mistakes

Using BEFORE instead of AFTER.

Confusing event types or trigger levels.

The trigger fires AFTER INSERT on each ROW.

Practice

1. What is the main difference between a row-level trigger and a statement-level trigger in PostgreSQL?

easy

A. Row-level triggers only work on INSERT; statement-level triggers only work on UPDATE.

B. Row-level triggers execute once per SQL statement; statement-level triggers execute once for each affected row.

C. Row-level triggers execute once for each affected row; statement-level triggers execute once per SQL statement.

D. Row-level triggers cannot modify data; statement-level triggers can modify data.

Solution

1. Step 1: Understand trigger execution scope

   Row-level triggers run once for every row affected by the SQL command, meaning if 10 rows are updated, the trigger runs 10 times.

2. Step 2: Understand statement-level trigger behavior

   Statement-level triggers run only once per SQL command, regardless of how many rows are affected.

3. Final Answer:

   Row-level triggers execute once for each affected row; statement-level triggers execute once per SQL statement. -> Option C

4. Quick Check:

   Row-level = per row, Statement-level = per statement [OK]

Hint: Row-level = per row; statement-level = per statement [OK]

Common Mistakes:

• Confusing which trigger runs per row vs per statement
• Thinking row-level triggers run only once per statement
• Assuming statement-level triggers run per row
• Believing trigger types depend on operation type (INSERT/UPDATE)

2. Which of the following is the correct syntax to create a row-level trigger in PostgreSQL?

easy

A. CREATE TRIGGER trg AFTER INSERT ON table FOR EACH ROW EXECUTE FUNCTION func();

B. CREATE TRIGGER trg AFTER INSERT ON table FOR EACH STATEMENT EXECUTE FUNCTION func();

C. CREATE TRIGGER trg AFTER INSERT ON table EXECUTE FUNCTION func();

D. CREATE TRIGGER trg FOR EACH ROW EXECUTE FUNCTION func();

Solution

1. Step 1: Identify correct trigger syntax

   The syntax for creating a row-level trigger requires the clause FOR EACH ROW to specify it runs per affected row.

2. Step 2: Check full syntax correctness

   CREATE TRIGGER trg AFTER INSERT ON table FOR EACH ROW EXECUTE FUNCTION func(); correctly includes AFTER INSERT, ON table, FOR EACH ROW, and EXECUTE FUNCTION func(); which is the proper syntax.

3. Final Answer:

   CREATE TRIGGER trg AFTER INSERT ON table FOR EACH ROW EXECUTE FUNCTION func(); -> Option A

4. Quick Check:

   Row-level triggers use FOR EACH ROW [OK]

Hint: Row-level triggers always use FOR EACH ROW clause [OK]

Common Mistakes:

• Omitting FOR EACH ROW for row-level triggers
• Using FOR EACH STATEMENT for row-level triggers
• Missing EXECUTE FUNCTION keyword
• Incorrect order of clauses

3. Consider this trigger function and trigger:

CREATE FUNCTION trg_func() RETURNS trigger AS $$ BEGIN RAISE NOTICE 'Triggered'; RETURN NEW; END; $$ LANGUAGE plpgsql;
CREATE TRIGGER trg AFTER UPDATE ON employees FOR EACH ROW EXECUTE FUNCTION trg_func();
UPDATE employees SET salary = salary * 1.1 WHERE department = 'Sales';

What will be the output when the UPDATE affects 3 rows?

medium

A. The notice 'Triggered' will appear 3 times.

B. The notice 'Triggered' will appear once.

C. No notice will appear because AFTER UPDATE triggers do not raise notices.

D. The notice 'Triggered' will appear once per statement plus once per row.

Solution

1. Step 1: Identify trigger type and execution count

   The trigger is defined FOR EACH ROW, so it runs once for every row updated.

2. Step 2: Calculate total trigger executions

   Since 3 rows are updated, the trigger function runs 3 times, each raising the notice 'Triggered'.

3. Final Answer:

   The notice 'Triggered' will appear 3 times. -> Option A

4. Quick Check:

   Row-level trigger runs per row = 3 notices [OK]

Hint: FOR EACH ROW triggers run once per affected row [OK]

Common Mistakes:

• Assuming notice appears only once per statement
• Confusing FOR EACH ROW with FOR EACH STATEMENT
• Thinking AFTER UPDATE triggers don't raise notices
• Believing trigger runs multiple times per row

4. You created a statement-level trigger but it seems to run multiple times when you update multiple rows. What is the most likely cause?

medium

A. PostgreSQL does not support statement-level triggers.

B. Statement-level triggers always run once per row by design.

C. The trigger function contains a loop causing multiple executions.

D. You accidentally defined the trigger as FOR EACH ROW instead of FOR EACH STATEMENT.

Solution

1. Step 1: Understand trigger definition impact

   If a trigger runs multiple times per row update, it is likely defined as FOR EACH ROW, not FOR EACH STATEMENT.

2. Step 2: Verify PostgreSQL trigger capabilities

   PostgreSQL supports both row-level and statement-level triggers; statement-level triggers run once per statement.

3. Final Answer:

   You accidentally defined the trigger as FOR EACH ROW instead of FOR EACH STATEMENT. -> Option D

4. Quick Check:

   FOR EACH ROW triggers run per row, causing multiple executions [OK]

Hint: Check FOR EACH ROW vs FOR EACH STATEMENT clause [OK]

Common Mistakes:

• Believing statement-level triggers run per row
• Ignoring trigger definition syntax
• Assuming PostgreSQL lacks statement-level triggers
• Blaming trigger function code without checking trigger type

5. You want to log a summary message once after any UPDATE statement on a table, regardless of how many rows are changed. Which trigger type and timing should you use?

hard

A. A BEFORE UPDATE row-level trigger

B. An AFTER UPDATE statement-level trigger

C. An AFTER UPDATE row-level trigger

D. A BEFORE UPDATE statement-level trigger

Solution

1. Step 1: Determine trigger timing for logging after update

   Logging after the update completes requires an AFTER trigger.

2. Step 2: Choose trigger level for single summary message

   To log once per statement regardless of rows, use a statement-level trigger (FOR EACH STATEMENT).

3. Final Answer:

   An AFTER UPDATE statement-level trigger -> Option B

4. Quick Check:

   Summary logging = AFTER + statement-level trigger [OK]

Hint: Use AFTER statement-level trigger for single summary action [OK]

Common Mistakes:

• Using row-level triggers causing multiple logs
• Using BEFORE triggers missing final state
• Confusing timing and level for logging
• Assuming row-level triggers can log once per statement