Views with CHECK OPTION in PostgreSQL - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a view in a database?

A view is like a window to see data from one or more tables. It shows data without storing it separately.

beginner

What does the CHECK OPTION do in a view?

CHECK OPTION makes sure that any new or changed data through the view still fits the view's rules.

intermediate

Why use WITH CHECK OPTION in a view?

It stops users from adding or changing rows that don't match the view's filter conditions.

intermediate

Can you update a view without WITH CHECK OPTION?

Yes, but updates might add rows that don't follow the view's rules, causing confusion.

intermediate

Example: What happens if you try to insert a row through a view with CHECK OPTION that doesn't meet the view's filter?

The database will reject the insert because the row doesn't satisfy the view's conditions.

What does WITH CHECK OPTION ensure in a view?

A Only rows matching the view's filter can be inserted or updated through the view

B The view stores data separately

C The view cannot be queried

D The view automatically updates all tables

WITH CHECK OPTION ensures that any inserted or updated rows through the view meet the view's filter conditions.

If a view filters rows where status = 'active', what happens if you try to insert a row with status = 'inactive' through the view with CHECK OPTION?

A The insert fails

B The insert succeeds

C The row is inserted but hidden

D The database crashes

The insert fails because the row does not meet the view's filter condition enforced by CHECK OPTION.

Can you update rows through a view with CHECK OPTION to values outside the view's filter?

A Only if the table allows it

B Yes, always

C No, updates violating the filter are rejected

D Only if the view is read-only

Updates that would make rows not match the view's filter are rejected when WITH CHECK OPTION is used.

What happens if you create a view without WITH CHECK OPTION and update rows through it?

A Updates are always rejected

B Updates can add rows that don't match the view's filter

C The view automatically adds CHECK OPTION

D The view becomes read-only

Without WITH CHECK OPTION, updates can add rows that don't meet the view's filter, which can cause inconsistent data views.

Which SQL keyword is used to enforce that changes through a view meet its filter conditions?

A WITH VALIDATION

B WITH FILTER

C WITH RESTRICTION

D WITH CHECK OPTION

The keyword WITH CHECK OPTION enforces that inserts and updates through the view meet the view's filter conditions.

Explain in your own words what WITH CHECK OPTION does when used in a view.

Think about how the view controls what data can be changed through it.

Describe a real-life example where using WITH CHECK OPTION in a view would be helpful.

Imagine a list of active users where you don't want inactive users added by mistake.

Practice

1. What is the main purpose of using WITH CHECK OPTION in a PostgreSQL view?

easy

A. To prevent inserts or updates that violate the view's filter conditions

B. To speed up query execution on the view

C. To allow views to be updated without restrictions

D. To create a temporary table instead of a view

Solution

1. Step 1: Understand the role of WITH CHECK OPTION

   This option ensures that any data inserted or updated through the view must satisfy the view's filter conditions.

2. Step 2: Identify what it prevents

   It prevents changes that would cause rows to fall outside the view's defined criteria, keeping data consistent.

3. Final Answer:

   To prevent inserts or updates that violate the view's filter conditions -> Option A

4. Quick Check:

   WITH CHECK OPTION blocks invalid changes = A [OK]

Hint: Check option stops changes outside view filters [OK]

Common Mistakes:

• Thinking it speeds up queries
• Believing it allows unrestricted updates
• Confusing it with temporary tables

2. Which of the following is the correct syntax to create a view with a WITH CHECK OPTION in PostgreSQL?

easy

A. CREATE VIEW v AS SELECT * FROM t WHERE x > 10, WITH CHECK OPTION;

B. CREATE VIEW v AS SELECT * FROM t WHERE x > 10 CHECK OPTION WITH;

C. CREATE VIEW v AS SELECT * FROM t WHERE x > 10 WITH CHECK OPTION;

D. CREATE VIEW v AS SELECT * FROM t WHERE x > 10 OPTION CHECK WITH;

Solution

1. Step 1: Recall PostgreSQL view creation syntax

   The correct syntax places WITH CHECK OPTION at the end of the CREATE VIEW statement.

2. Step 2: Match the exact phrase and order

   CREATE VIEW v AS SELECT * FROM t WHERE x > 10 WITH CHECK OPTION; matches the correct syntax: CREATE VIEW v AS SELECT ... WITH CHECK OPTION;

3. Final Answer:

   CREATE VIEW v AS SELECT * FROM t WHERE x > 10 WITH CHECK OPTION; -> Option C

4. Quick Check:

   Correct syntax ends with WITH CHECK OPTION [OK]

Hint: WITH CHECK OPTION always goes at the end of CREATE VIEW [OK]

Common Mistakes:

• Swapping words order
• Adding semicolons inside SELECT
• Using incorrect keywords order

3. Given the table employees(id, name, salary) and the view:
CREATE VIEW high_salary AS SELECT * FROM employees WHERE salary > 5000 WITH CHECK OPTION;
What happens if you try to insert (10, 'Anna', 4000) into high_salary?

medium

A. The insert fails due to the CHECK OPTION

B. The insert succeeds but the row is not visible in the view

C. The insert succeeds and adds the row

D. The insert causes a syntax error

Solution

1. Step 1: Understand the view filter and CHECK OPTION

   The view only shows employees with salary > 5000, and WITH CHECK OPTION prevents inserts that don't meet this.

2. Step 2: Analyze the insert data

   The salary 4000 is less than 5000, so the insert violates the view's filter and is blocked.

3. Final Answer:

   The insert fails due to the CHECK OPTION -> Option A

4. Quick Check:

   Insert violating view filter blocked = C [OK]

Hint: Insert must meet view filter or it fails [OK]

Common Mistakes:

• Thinking insert always succeeds
• Assuming row is added but hidden
• Confusing syntax error with runtime error

4. You have this view:
CREATE VIEW active_users AS SELECT * FROM users WHERE active = true WITH CHECK OPTION;
You try to update a row through the view to set active = false. What is the result?

medium

A. The update succeeds and changes the row

B. The update causes a syntax error

C. The update succeeds but the row disappears from the view

D. The update fails because it violates the CHECK OPTION

Solution

1. Step 1: Understand the view filter and update

   The view only shows rows where active = true. WITH CHECK OPTION blocks updates that break this condition.

2. Step 2: Analyze the attempted update

   Setting active = false violates the view filter, so the update is rejected.

3. Final Answer:

   The update fails because it violates the CHECK OPTION -> Option D

4. Quick Check:

   Update violating view filter blocked = B [OK]

Hint: Updates must keep rows inside view filter [OK]

Common Mistakes:

• Assuming update succeeds but hides row
• Confusing syntax error with constraint error
• Ignoring CHECK OPTION effect on updates

5. Consider a view CREATE VIEW vip_customers AS SELECT * FROM customers WHERE vip = true WITH CHECK OPTION;
You want to allow inserting new customers through this view only if they are VIPs. Which of the following statements correctly inserts a VIP customer and rejects a non-VIP customer?

hard

A. INSERT INTO vip_customers (id, name, vip) VALUES (1, 'John', false); -- failsINSERT INTO vip_customers (id, name, vip) VALUES (2, 'Jane', false); -- fails

B. INSERT INTO vip_customers (id, name, vip) VALUES (1, 'John', true); -- succeedsINSERT INTO vip_customers (id, name, vip) VALUES (2, 'Jane', false); -- fails

C. INSERT INTO vip_customers (id, name, vip) VALUES (1, 'John', true); -- failsINSERT INTO vip_customers (id, name, vip) VALUES (2, 'Jane', false); -- succeeds

D. INSERT INTO vip_customers (id, name, vip) VALUES (1, 'John', false); -- succeedsINSERT INTO vip_customers (id, name, vip) VALUES (2, 'Jane', true); -- fails

Solution

1. Step 1: Understand the view filter and CHECK OPTION

   The view only allows rows where vip = true. WITH CHECK OPTION blocks inserts with vip = false.

2. Step 2: Analyze each insert statement

   Inserting John with vip = true succeeds. Inserting Jane with vip = false fails due to CHECK OPTION.

3. Final Answer:

   Only inserts with vip = true succeed; others fail -> Option B

4. Quick Check:

   Insert vip=true allowed, vip=false blocked = D [OK]

Hint: Only insert rows matching view filter pass CHECK OPTION [OK]

Common Mistakes:

• Trying to insert non-VIP through VIP view
• Assuming all inserts succeed
• Confusing which values pass CHECK OPTION