PostgreSQL - Triggers in PostgreSQL
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?
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📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Determine trigger timing for logging after update
Logging after the update completes requires an AFTER trigger.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).Final Answer:
An AFTER UPDATE statement-level trigger -> Option BQuick Check:
Summary logging = AFTER + statement-level trigger [OK]
Quick Trick: 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
Master "Triggers in PostgreSQL" in PostgreSQL
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore PostgreSQL Quizzes