Updatable views in PostgreSQL - Time & Space Complexity

Time Complexity: Updatable views

O(n)

Understanding Time Complexity

When working with updatable views in PostgreSQL, it's important to understand how the time to update data changes as the size of the underlying tables grows.

We want to know how the cost of updating through a view scales with more data.

Scenario Under Consideration

Analyze the time complexity of updating data through a simple updatable view.

CREATE VIEW employee_view AS
  SELECT id, name, salary FROM employees;

UPDATE employee_view
SET salary = salary * 1.1
WHERE id = 123;
    

This code updates the salary of one employee through a view that directly reflects the employees table.

Identify Repeating Operations

Look for repeated actions that affect performance.

• Primary operation: Searching for the row with the matching id in the employees table.
• How many times: Once per update, but the search may scan multiple rows depending on indexing.

How Execution Grows With Input

As the employees table grows, finding the row to update can take longer if there is no index.

Input Size (n)	Approx. Operations
10	10 (search through 10 rows)
100	100 (search through 100 rows)
1000	1000 (search through 1000 rows)

Pattern observation: Without an index, the search grows linearly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to update grows in direct proportion to the number of rows in the table when no index is used.

Common Mistake

[X] Wrong: "Updating through a view always takes constant time regardless of table size."

[OK] Correct: The update must find the correct row in the underlying table, which can take longer as the table grows if no index helps.

Interview Connect

Understanding how updates through views scale helps you explain database behavior clearly and shows you grasp practical performance considerations.

Self-Check

What if we added an index on the id column? How would the time complexity change?

Practice

1. What is an updatable view in PostgreSQL?

easy

A. A function that returns a set of rows

B. A view that only shows data but cannot be changed

C. A table that stores data permanently

D. A view that allows you to change data in the underlying table through it

Solution

1. Step 1: Understand the definition of a view

   A view is a saved query that shows data from one or more tables.

2. Step 2: Identify what makes a view updatable

   An updatable view lets you change data in the underlying table by modifying the view.

3. Final Answer:

   A view that allows you to change data in the underlying table through it -> Option D

4. Quick Check:

   Updatable view = change data through view [OK]

Hint: Updatable views let you edit data through the view [OK]

Common Mistakes:

• Confusing views with tables
• Thinking all views are read-only
• Believing views store data themselves

2. Which of the following is the correct syntax to create a simple updatable view on a single table employees showing id and name columns?

easy

A. CREATE VIEW emp_view AS SELECT id, name FROM employees;

B. CREATE VIEW emp_view AS UPDATE employees SET name = 'John';

C. CREATE TABLE emp_view AS SELECT id, name FROM employees;

D. CREATE FUNCTION emp_view() RETURNS TABLE(id INT, name TEXT) AS $$ SELECT id, name FROM employees; $$ LANGUAGE SQL;

Solution

1. Step 1: Recall the syntax to create a view

   The syntax is CREATE VIEW view_name AS SELECT columns FROM table;

2. Step 2: Check each option

   CREATE VIEW emp_view AS SELECT id, name FROM employees; matches the correct syntax for a simple view. The other options are incorrect because they use UPDATE, CREATE TABLE, or FUNCTION instead of CREATE VIEW.

3. Final Answer:

   CREATE VIEW emp_view AS SELECT id, name FROM employees; -> Option A

4. Quick Check:

   CREATE VIEW uses SELECT query [OK]

Hint: CREATE VIEW uses SELECT, not UPDATE or TABLE [OK]

Common Mistakes:

• Using UPDATE instead of SELECT in CREATE VIEW
• Confusing CREATE VIEW with CREATE TABLE
• Trying to create a function instead of a view

3. Given the table products(id, name, price) and the view CREATE VIEW cheap_products AS SELECT id, name FROM products WHERE price < 100; What happens if you try to update the name of a product through cheap_products view?

medium

A. The update changes only the view but not the underlying table

B. The update fails because the view filters rows with a WHERE clause

C. The update succeeds and changes the product name in the products table

D. The update causes a syntax error

Solution

1. Step 1: Understand updatable views with WHERE clause

   Views that select from a single base table with a restricting WHERE clause are updatable in PostgreSQL.

2. Step 2: Check the effect of updating through filtered view

   Updating the name of a product visible in the view (price < 100) will successfully update the underlying products table.

3. Final Answer:

   The update succeeds and changes the product name in the products table -> Option C

4. Quick Check:

   Single-table views with WHERE are updatable [OK]

Hint: Single-table views with WHERE filters are updatable [OK]

Common Mistakes:

• Thinking WHERE clause prevents updates
• Thinking update affects only the view
• Expecting syntax error instead of runtime error

4. You created a view with this SQL:
CREATE VIEW emp_dept AS SELECT e.id, e.name, d.name AS dept_name FROM employees e JOIN departments d ON e.dept_id = d.id;
When you try to update emp_dept to change an employee's name, you get an error. What is the main reason?

medium

A. The view joins multiple tables, so it is not automatically updatable

B. The view does not include the employee's ID column

C. The view uses aliases for columns, causing syntax errors

D. The view is missing a WHERE clause

Solution

1. Step 1: Analyze the view definition

   The view joins two tables: employees and departments.

2. Step 2: Understand updatable view rules for joins

   Views that join multiple tables are not automatically updatable in PostgreSQL because the system cannot decide how to update multiple tables from one view.

3. Final Answer:

   The view joins multiple tables, so it is not automatically updatable -> Option A

4. Quick Check:

   Joined views are not updatable by default [OK]

Hint: Views with joins are not updatable automatically [OK]

Common Mistakes:

• Thinking missing ID causes update failure
• Blaming column aliases for errors
• Assuming WHERE clause is required for updates

5. You want to make a complex view updatable that joins orders and customers tables. Which PostgreSQL feature should you use to allow updates through this view?

hard

A. Use a materialized view instead of a regular view

B. Create INSTEAD OF triggers on the view to handle updates

C. Add a WHERE clause to the view to filter rows

D. Create a function that returns the joined data

Solution

1. Step 1: Understand limitations of updatable views with joins

   Views joining multiple tables are not automatically updatable in PostgreSQL.

2. Step 2: Use INSTEAD OF triggers to enable updates

   INSTEAD OF triggers let you define custom update logic on complex views, making them updatable.

3. Final Answer:

   Create INSTEAD OF triggers on the view to handle updates -> Option B

4. Quick Check:

   INSTEAD OF triggers enable updates on complex views [OK]

Hint: Use INSTEAD OF triggers for complex view updates [OK]

Common Mistakes:

• Thinking WHERE clause makes view updatable
• Confusing materialized views with updatable views
• Believing functions replace update triggers