Querying from views in MySQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

Output of querying a simple view

Given a view EmployeeView defined as CREATE VIEW EmployeeView AS SELECT id, name, salary FROM Employees WHERE salary > 50000;, what will be the output of SELECT * FROM EmployeeView WHERE name = 'Alice'; if the Employees table contains:

id | name | salary
1 | Alice | 60000
2 | Bob | 45000
3 | Carol | 70000

A No rows returned

B 2 rows: id=1, name='Alice', salary=60000 and id=3, name='Carol', salary=70000

C 3 rows: all employees regardless of salary

D 1 row: id=1, name='Alice', salary=60000

💡 Hint

Remember the view filters employees with salary greater than 50000.

The view only includes employees with salary above 50000. Among them, only Alice matches the name filter.

📝 Syntax

intermediate

Identify the syntax error in querying a view

Which of the following queries will cause a syntax error when querying a view named ProductView?

A SELECT * FROM ProductView WHERE price > 100;

B SELECT * ProductView WHERE price > 100;

C SELECT * FROM ProductView GROUP BY category;

D SELECT price, name FROM ProductView;

💡 Hint

Check the basic SELECT syntax for missing keywords.

Option B is missing the FROM keyword, causing a syntax error.

❓ optimization

advanced

Optimizing queries on views with joins

Consider a view OrderSummary defined as:
CREATE VIEW OrderSummary AS SELECT o.id, c.name, o.total FROM Orders o JOIN Customers c ON o.customer_id = c.id;
Which query will be the most efficient to get orders with total > 1000?

A SELECT o.id, c.name, o.total FROM Orders o JOIN Customers c ON o.customer_id = c.id WHERE o.total > 1000;

B SELECT * FROM OrderSummary HAVING total > 1000;

C SELECT * FROM OrderSummary WHERE total > 1000;

D SELECT * FROM OrderSummary WHERE total < 1000;

💡 Hint

Filtering before joining can improve performance.

Option A filters orders before joining, reducing data processed. Option A filters after the view's join, which may be less efficient.

🔧 Debug

advanced

Debugging incorrect results from a view query

A view ActiveUsers is defined as:
CREATE VIEW ActiveUsers AS SELECT id, username FROM Users WHERE status = 'active';
Running SELECT * FROM ActiveUsers WHERE username LIKE '%admin%'; returns no rows, but you know there are active users with 'admin' in their username. What is the most likely cause?

A The query is case-sensitive and usernames have different case.

B The Users table has no active users with 'admin' in username.

C The view definition filters out users with 'admin' in username.

D The LIKE operator is not supported in views.

💡 Hint

Consider how string matching works in SQL.

The LIKE operator is case-sensitive in many MySQL configurations, so 'Admin' won't match '%admin%'.

🧠 Conceptual

expert

Understanding limitations of updatable views

Which of the following statements about updatable views in MySQL is TRUE?

A Views with GROUP BY clauses are always updatable.

B Views that join multiple tables can never be updated directly.

C Views that select from a single table without aggregation can be updatable.

D Views without a primary key cannot be updated.

💡 Hint

Think about when MySQL allows updates through views.

MySQL allows updates on views that select from a single table without aggregation or grouping.

Practice

1. What is a view in MySQL?

easy

A. A virtual table based on a stored query

B. A physical table storing data permanently

C. A backup of a database

D. A user account with special permissions

Solution

1. Step 1: Understand the definition of a view

   A view is not a physical table but a saved query that acts like a table.

2. Step 2: Differentiate from other options

   Options A, B, and C describe physical tables, backups, or users, which are not views.

3. Final Answer:

   A virtual table based on a stored query -> Option A

4. Quick Check:

   View = virtual table [OK]

Hint: Remember: Views are saved queries, not real tables [OK]

Common Mistakes:

• Thinking views store data physically
• Confusing views with backups
• Assuming views are user accounts

2. Which of the following is the correct syntax to select all columns from a view named employee_view?

easy

A. SELECT ALL FROM employee_view;

B. SELECT * FROM VIEW employee_view;

C. SELECT * FROM employee_view;

D. GET * FROM employee_view;

Solution

1. Step 1: Recall standard SELECT syntax for views

   Views are queried like tables using SELECT * FROM view_name;

2. Step 2: Check each option's syntax

   SELECT * FROM employee_view; uses correct syntax. Options B, C, and D use invalid keywords or order.

3. Final Answer:

   SELECT * FROM employee_view; -> Option C

4. Quick Check:

   SELECT * FROM view_name; is correct [OK]

Hint: Query views like tables using SELECT * FROM view_name [OK]

Common Mistakes:

• Using VIEW keyword in SELECT statement
• Replacing SELECT with GET
• Using SELECT ALL instead of SELECT *

3. Given a view sales_view defined as SELECT product_id, SUM(quantity) AS total_qty FROM sales GROUP BY product_id, what will the query SELECT * FROM sales_view WHERE total_qty > 100; return?

medium

A. All products with total quantity sold greater than 100

B. All sales records with quantity greater than 100

C. Syntax error because WHERE cannot be used on views

D. Empty result because total_qty is not a column

Solution

1. Step 1: Understand the view definition

   The view groups sales by product_id and sums quantity as total_qty.

2. Step 2: Analyze the query on the view

   The query filters rows where total_qty > 100, so it returns products with total sales over 100.

3. Final Answer:

   All products with total quantity sold greater than 100 -> Option A

4. Quick Check:

   Filtering on view columns works normally [OK]

Hint: Filter views like tables using WHERE on view columns [OK]

Common Mistakes:

• Thinking WHERE can't be used on views
• Confusing total_qty with original quantity column
• Assuming syntax error due to aggregation

4. You have a view customer_view defined as SELECT id, name, email FROM customers; but running SELECT phone FROM customer_view; gives an error. What is the problem?

medium

A. Views cannot be queried for single columns

B. The column phone does not exist in the view

C. You must use SELECT * to query views

D. The view is corrupted and needs to be recreated

Solution

1. Step 1: Check the view's defined columns

   The view only includes id, name, and email columns, no phone column.

2. Step 2: Understand the error cause

   Querying a column not in the view causes an error because it doesn't exist in the virtual table.

3. Final Answer:

   The column phone does not exist in the view -> Option B

4. Quick Check:

   Query columns must exist in view definition [OK]

Hint: Check view columns before selecting them [OK]

Common Mistakes:

• Assuming views allow any column selection
• Thinking views are corrupted if column missing
• Believing SELECT * is mandatory for views

5. You want to create a view active_users_view that shows only users with status = 'active' from the users table. Which query correctly creates this view?

hard

A. CREATE VIEW active_users_view AS SELECT * FROM users WHERE status == 'active';

B. CREATE VIEW active_users_view SELECT * FROM users WHERE status = 'active';

C. CREATE VIEW active_users_view AS SELECT * FROM users HAVING status = 'active';

D. CREATE VIEW active_users_view AS SELECT * FROM users WHERE status = 'active';

Solution

1. Step 1: Recall correct CREATE VIEW syntax

   The syntax requires CREATE VIEW view_name AS SELECT ... WHERE ...

2. Step 2: Check each option's correctness

   CREATE VIEW active_users_view AS SELECT * FROM users WHERE status = 'active'; uses correct syntax with WHERE clause. CREATE VIEW active_users_view SELECT * FROM users WHERE status = 'active'; misses AS keyword. CREATE VIEW active_users_view AS SELECT * FROM users HAVING status = 'active'; wrongly uses HAVING without GROUP BY. CREATE VIEW active_users_view AS SELECT * FROM users WHERE status == 'active'; uses invalid '==' operator.

3. Final Answer:

   CREATE VIEW active_users_view AS SELECT * FROM users WHERE status = 'active'; -> Option D

4. Quick Check:

   CREATE VIEW ... AS SELECT ... WHERE ... is correct [OK]

Hint: Use WHERE, not HAVING, and '=' for conditions in views [OK]

Common Mistakes:

• Omitting AS keyword
• Using HAVING without GROUP BY
• Using '==' instead of '=' in conditions