A developer creates a view with CREATE VIEW emp_view AS SELECT id, name FROM employees; but gets an error when trying to update it. What could be a likely cause?

medium📝 Debug Q7 of 15

PostgreSQL - Views and Materialized Views

AThe employees table has no primary key defined.

BThe view uses SELECT * instead of explicit columns.

CThe view includes a WHERE clause filtering rows.

DThe view is created with the WITH CHECK OPTION.

Step-by-Step Solution

Solution:

Step 1: Check requirements for updatable views
PostgreSQL requires the underlying table to have a primary key or unique index for updates through views.
Step 2: Analyze the cause of error
If employees table lacks a primary key, updates through the view will fail.
Final Answer:
The employees table has no primary key defined. -> Option A
Quick Check:
Primary key needed for updatable views [OK]

Quick Trick: Ensure base table has primary key for updatable views [OK]

Common Mistakes:

Thinking SELECT * causes update errors
Assuming WHERE clause blocks updates
Confusing WITH CHECK OPTION with update errors

Master "Views and Materialized Views" in PostgreSQL

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

A developer creates a view with CREATE VIEW emp_view AS SELECT id, name FROM employees; but gets an error when trying to update it. What could be a likely cause?

Step 1: Check requirements for updatable views

Step 2: Analyze the cause of error

Final Answer:

Quick Check:

Want More Practice?