View limitations in MySQL - Time & Space Complexity

Time Complexity: View limitations

O(n)

Understanding Time Complexity

When using views in MySQL, it's important to understand how their performance changes as data grows.

We want to see how the time to get results from a view changes when the underlying data gets bigger.

Scenario Under Consideration

Analyze the time complexity of the following view query.

CREATE VIEW recent_orders AS
SELECT order_id, customer_id, order_date
FROM orders
WHERE order_date >= DATE_SUB(CURDATE(), INTERVAL 30 DAY);

SELECT * FROM recent_orders;
    

This view selects orders from the last 30 days and then retrieves all those recent orders.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning the orders table to find rows matching the date condition.
• How many times: Once per query execution, scanning all rows or using an index to filter.

How Execution Grows With Input

As the orders table grows, the time to filter recent orders grows roughly in proportion to the number of rows scanned.

Input Size (n)	Approx. Operations
10	About 10 rows checked
100	About 100 rows checked
1000	About 1000 rows checked

Pattern observation: The work grows roughly in a straight line as the table gets bigger.

Final Time Complexity

Time Complexity: O(n)

This means the time to get results grows directly with the number of rows in the orders table.

Common Mistake

[X] Wrong: "Views store data separately, so querying a view is always fast regardless of table size."

[OK] Correct: Views do not store data themselves; they run the underlying query each time, so performance depends on the base tables.

Interview Connect

Understanding how views work and their time cost helps you explain database design choices clearly and confidently.

Self-Check

"What if the view included a join with another large table? How would that affect the time complexity?"

Practice

1. Which of the following is true about MySQL views?

easy

A. Views always allow you to update data directly.

B. Views do not store data themselves; they show data from base tables.

C. Views can have indexes to speed up queries.

D. Views automatically create backup copies of data.

Solution

1. Step 1: Understand what a view is and check each option

   A view is a virtual table that shows data from one or more base tables but does not store data itself. Views do not store data themselves; they show data from base tables. matches the definition. Options A, C, and D are incorrect because views do not always allow updates, cannot have indexes, and do not store backup data.

2. Final Answer:

   Views do not store data themselves; they show data from base tables. -> Option B

3. Quick Check:

   Views are virtual tables = B [OK]

Hint: Remember: Views show data, they don't store it [OK]

Common Mistakes:

• Thinking views store data like tables
• Assuming views always allow updates
• Believing views can have indexes

2. Which of the following is the correct syntax to create a simple view in MySQL?

easy

A. CREATE VIEW AS SELECT * FROM table_name;

B. CREATE TABLE view_name AS SELECT * FROM table_name;

C. CREATE VIEW view_name FROM table_name;

D. CREATE VIEW view_name AS SELECT * FROM table_name;

Solution

1. Step 1: Recall the syntax for creating a view and compare options

   The correct syntax is: CREATE VIEW view_name AS SELECT ... CREATE VIEW view_name AS SELECT * FROM table_name; matches the correct syntax. CREATE TABLE view_name AS SELECT * FROM table_name; creates a table, not a view. CREATE VIEW view_name FROM table_name; has incorrect syntax.

2. Final Answer:

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

3. Quick Check:

   CREATE VIEW ... AS SELECT ... = D [OK]

Hint: Use 'CREATE VIEW name AS SELECT...' for views [OK]

Common Mistakes:

• Using CREATE TABLE instead of CREATE VIEW
• Omitting AS keyword
• Incorrect order of clauses

3. Given the view definition:
CREATE VIEW v_emp AS SELECT id, name FROM employees;
Which of the following queries will return the correct result?

medium

A. INSERT INTO v_emp (id, name) VALUES (6, 'Anna');

B. UPDATE v_emp SET name = 'John' WHERE id = 5;

C. SELECT * FROM v_emp WHERE id = 5;

D. DELETE FROM v_emp WHERE id = 5;

Solution

1. Step 1: Understand the view and its limitations, then analyze each query

   The view selects id and name from employees. Simple views on one table allow SELECT but may restrict UPDATE, INSERT, DELETE. SELECT * FROM v_emp WHERE id = 5; is a SELECT query and will work correctly. Options B, C, and D try to modify data through the view, which is often not allowed or restricted.

2. Final Answer:

   SELECT * FROM v_emp WHERE id = 5; -> Option C

3. Quick Check:

   Simple views allow SELECT only = A [OK]

Hint: Views usually allow SELECT, not data changes [OK]

Common Mistakes:

• Trying to update or insert through views without triggers
• Assuming all views are updatable
• Ignoring view restrictions on DELETE

4. You created a view with this statement:
CREATE VIEW v_sales AS SELECT order_id, customer_id, total FROM orders WHERE total > 100;
When you try to update the view with:
UPDATE v_sales SET total = 90 WHERE order_id = 10;
You get an error. What is the likely cause?

medium

A. The view contains a WHERE clause filtering rows, making it non-updatable.

B. You cannot update any view in MySQL.

C. The view does not include the primary key column.

D. The UPDATE syntax is incorrect for views.

Solution

1. Step 1: Identify view update restrictions and check the error cause

   Views with WHERE clauses or filtering conditions are often non-updatable because the database cannot guarantee consistent updates. The view contains a WHERE clause filtering rows, making it non-updatable. explains the error correctly. You cannot update any view in MySQL. is false because some views are updatable. The view does not include the primary key column. is incorrect because order_id is included. The UPDATE syntax is incorrect for views. is wrong as syntax is valid.

2. Final Answer:

   The view contains a WHERE clause filtering rows, making it non-updatable. -> Option A

3. Quick Check:

   WHERE clause in view blocks updates = A [OK]

Hint: Views with filters often block updates [OK]

Common Mistakes:

• Assuming all views are updatable
• Blaming syntax instead of view definition
• Ignoring WHERE clause effect on updates

5. You want to create a view that allows updating the salary column of employees but also shows the department name from a joined table. Which approach respects MySQL view limitations?

hard

A. Create a simple view on employees only, then update salary directly on employees table.

B. Create a view joining employees and departments, then update salary through the view.

C. Create a view with a WHERE clause filtering departments, then update salary through it.

D. Create a view with GROUP BY on departments and update salary through the view.

Solution

1. Step 1: Understand update restrictions on views with joins and choose the approach that allows updates

   Views that join multiple tables or use GROUP BY are generally non-updatable in MySQL. Create a simple view on employees only, then update salary directly on employees table. creates a simple view on one table, allowing updates on salary by updating the base table directly. Options A, B, and D involve joins, filters, or grouping, which block updates.

2. Final Answer:

   Create a simple view on employees only, then update salary directly on employees table. -> Option A

3. Quick Check:

   Simple single-table views allow updates = C [OK]

Hint: Update only through simple single-table views [OK]

Common Mistakes:

• Trying to update through joined or grouped views
• Assuming filters don't block updates
• Ignoring base table updates