Bird
0
0

Why might a database designer choose ON UPDATE CASCADE over ON UPDATE RESTRICT for a foreign key?

hard📝 Conceptual Q10 of 15
SQL - Table Constraints
Why might a database designer choose ON UPDATE CASCADE over ON UPDATE RESTRICT for a foreign key?
ATo prevent any changes to parent keys if children exist.
BTo automatically keep child foreign keys in sync when parent keys change.
CTo set child foreign keys to NULL when parent keys change.
DTo improve query performance on joins.
Step-by-Step Solution
Solution:
  1. Step 1: Understand ON UPDATE CASCADE purpose

    ON UPDATE CASCADE automatically updates child foreign keys when parent keys change.
  2. Step 2: Compare with ON UPDATE RESTRICT

    ON UPDATE RESTRICT blocks parent key changes if children exist, preventing automatic sync.
  3. Final Answer:

    To automatically keep child foreign keys in sync when parent keys change. -> Option B
  4. Quick Check:

    ON UPDATE CASCADE syncs keys automatically [OK]
Quick Trick: CASCADE keeps keys synced automatically [OK]
Common Mistakes:
MISTAKES
  • Confusing CASCADE with RESTRICT
  • Thinking CASCADE sets keys to NULL
  • Assuming CASCADE improves performance

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More SQL Quizzes