Updatable views in MySQL - Time & Space Complexity

Time Complexity: Updatable views

O(n)

Understanding Time Complexity

When we update data through a view in MySQL, it is important to understand how the database processes these updates.

We want to know how the time to update grows as the data behind the view grows.

Scenario Under Consideration

Analyze the time complexity of updating data through an updatable view.

CREATE VIEW employee_view AS
SELECT id, name, salary
FROM employees
WHERE department = 'Sales';

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

This code creates a view showing sales employees and then updates the salary of one employee through the view.

Identify Repeating Operations

Look for repeated steps when the update runs.

• Primary operation: Searching the base table for the matching row to update.
• How many times: The update targets one row, so the search depends on how the database finds that row.

How Execution Grows With Input

As the number of employees grows, the time to find the row may change.

Input Size (n)	Approx. Operations
10	About 10 checks if no index
100	About 100 checks if no index
1000	About 1000 checks if no index

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 through the view grows roughly in direct proportion to the number of rows in the base table.

Common Mistake

[X] Wrong: "Updating through a view is always faster because it looks simpler."

[OK] Correct: The view is just a window to the base table; the database still needs to find and update the actual data, which can take time depending on the table size.

Interview Connect

Understanding how updates through views work helps you explain database behavior clearly and shows you know how data access affects performance.

Self-Check

"What if the base table had an index on the 'id' column? How would that change the time complexity of the update through the view?"

Practice

1. What is an updatable view in MySQL?

easy

A. A view that only shows data but does not allow any changes.

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

C. A view that automatically creates new tables.

D. A view that stores data separately from the original table.

Solution

1. Step 1: Understand what a view is

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

2. Step 2: Define updatable view

   An updatable view lets you change data in the underlying table through the view itself.

3. Final Answer:

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

4. Quick Check:

   Updatable view = allows data change [OK]

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

Common Mistakes:

• Thinking views store data separately
• Confusing read-only views with updatable views
• Assuming all views are updatable

2. Which of the following is the correct syntax to create an updatable view in MySQL?

easy

A. CREATE VIEW view_name UPDATEABLE AS SELECT * FROM table_name;

B. CREATE UPDATABLE VIEW view_name AS SELECT * FROM table_name;

C. CREATE VIEW view_name WITH UPDATE AS SELECT * FROM table_name;

D. CREATE VIEW view_name AS SELECT * FROM table_name;

Solution

1. Step 1: Recall MySQL view creation syntax

   MySQL uses CREATE VIEW view_name AS SELECT ... to create views.

2. Step 2: Understand updatable views syntax

   There is no special keyword for updatable views; they are updatable if the SELECT is simple enough.

3. Final Answer:

   CREATE VIEW view_name AS SELECT * FROM table_name; -> Option D

4. Quick Check:

   Standard CREATE VIEW syntax = CREATE VIEW view_name AS SELECT * FROM table_name; [OK]

Hint: No special keyword needed; simple CREATE VIEW works [OK]

Common Mistakes:

• Adding non-existent keywords like UPDATABLE or WITH UPDATE
• Using wrong syntax keywords
• Assuming updatable views need special creation syntax

3. Given the table employees(id, name, salary) and the view:
CREATE VIEW emp_view AS SELECT id, name FROM employees;
Which of the following statements will succeed?

medium

A. UPDATE emp_view SET name = 'Alice' WHERE id = 1;

B. INSERT INTO emp_view (id, name) VALUES (4, 'Bob');

C. DELETE FROM emp_view WHERE salary = 2000;

D. UPDATE emp_view SET salary = 5000 WHERE id = 3;

Solution

1. Step 1: Check view columns and underlying table

   The view selects only id and name, excluding salary.

2. Step 2: Determine which operations are allowed

   Updating name through the view is allowed because it maps directly to the table column.
   INSERT fails (missing salary, assuming NOT NULL no default).
   DELETE referencing salary fails because salary not in view.
   Updating salary fails because salary not in view.

3. Final Answer:

   UPDATE emp_view SET name = 'Alice' WHERE id = 1; -> Option A

4. Quick Check:

   Update on view columns allowed = UPDATE emp_view SET name = 'Alice' WHERE id = 1; [OK]

Hint: You can update only columns included in the view [OK]

Common Mistakes:

• Trying to update columns not in the view
• Assuming inserts/deletes always work on views
• Ignoring missing columns in the view

4. You created a view with:
CREATE VIEW v AS SELECT id, name FROM employees WHERE salary > 3000;
Why does the statement UPDATE v SET salary = 5000 WHERE id = 5; fail?

medium

A. Because the view does not include the salary column.

B. Because the view has a WHERE clause, making it non-updatable.

C. Because you cannot update views with more than one column.

D. Because the view name is invalid.

Solution

1. Step 1: Check the columns in the view and the UPDATE target

   The view selects only id and name; salary is excluded.

2. Step 2: Check other options

   A WHERE clause does not prevent updates to included columns.
   Views can have multiple columns and be updatable.
   The view name is valid.

3. Final Answer:

   Because the view does not include the salary column. -> Option A

4. Quick Check:

   Cannot update column not in view [OK]

Hint: Cannot modify columns absent from the view [OK]

Common Mistakes:

• Thinking WHERE clause blocks updates
• Assuming multiple columns prevent updates
• Ignoring missing columns in the view

5. You want to create an updatable view on the orders table that shows only order_id and customer_id. You also want to allow updates to customer_id through the view. Which of the following is the best approach?

hard

A. CREATE VIEW order_view AS SELECT order_id FROM orders; Then update customer_id through order_view.

B. CREATE VIEW order_view AS SELECT order_id, customer_id FROM orders WHERE order_date > '2023-01-01'; Then update customer_id through order_view.

C. CREATE VIEW order_view AS SELECT order_id, customer_id FROM orders; Then update customer_id through order_view.

D. CREATE VIEW order_view AS SELECT order_id, customer_id, total FROM orders; Then update customer_id through order_view.

Solution

1. Step 1: Identify columns needed in the view

   The view must include customer_id to allow updates on it.

2. Step 2: Avoid issues that limit updatability or scope

   Adding a WHERE clause (as in B) limits updates to only recent orders.
   Including extra columns (as in C) shows more than requested.
   Excluding customer_id (as in A) prevents updating it.
   D provides exactly the requested columns without restrictions.

3. Final Answer:

   CREATE VIEW order_view AS SELECT order_id, customer_id FROM orders; Then update customer_id through order_view. -> Option C

4. Quick Check:

   Simple view with needed columns = updatable [OK]

Hint: Include columns to update, avoid WHERE filters [OK]

Common Mistakes:

• Adding WHERE filters that limit updates
• Excluding columns you want to update
• Adding unnecessary columns that confuse