Querying from views in MySQL - Step-by-Step Execution

Concept Flow - Querying from views

Create View

↓

Store View Definition

↓

Run Query on View

↓

Database Expands View to Base Tables

↓

Execute Expanded Query

↓

Return Result Set

A view is a saved query. When you query a view, the database runs the saved query behind the scenes and returns the results.

Execution Sample

MySQL

CREATE VIEW active_customers AS
SELECT id, name FROM customers WHERE active = 1;

SELECT * FROM active_customers;

Create a view named active_customers showing only active customers, then select all rows from that view.

Execution Table

Step	Action	Query/Condition	Result/Output
1	Create view	CREATE VIEW active_customers AS SELECT id, name FROM customers WHERE active = 1;	View 'active_customers' saved with definition
2	Query view	SELECT * FROM active_customers;	Database expands to SELECT id, name FROM customers WHERE active = 1;
3	Execute expanded query	SELECT id, name FROM customers WHERE active = 1;	Returns rows where active=1
4	Return result	Result set from expanded query	[{"id":1, "name":"Alice"}, {"id":3, "name":"Charlie"}]
5	End	No more steps	Query complete

💡 Query ends after returning all rows matching the view's condition

Variable Tracker

Variable	Start	After Step 2	After Step 3	Final
View Definition	None	SELECT id, name FROM customers WHERE active = 1	Same	Same
Query	SELECT * FROM active_customers	Expanded to SELECT id, name FROM customers WHERE active = 1	Executed	Result set returned
Result Set	Empty	Empty	[{"id":1, "name":"Alice"}, {"id":3, "name":"Charlie"}]	Returned to user

Key Moments - 2 Insights

Why does querying a view run a different query behind the scenes?

Because a view stores a saved query definition. When you query the view, the database replaces the view name with its saved query and runs that expanded query (see execution_table step 2).

Does the view store data itself?

No, the view only stores the query definition, not data. Data is fetched fresh from base tables each time you query the view (see variable_tracker 'View Definition' vs 'Result Set').

Visual Quiz - 3 Questions

Look at the execution_table, what query does the database actually run when you query the view?

A SELECT * FROM active_customers

B CREATE VIEW active_customers AS SELECT id, name FROM customers WHERE active = 1

C SELECT id, name FROM customers WHERE active = 1

D SELECT id, name FROM customers

💡 Hint

Check execution_table step 2 where the view query is expanded

At which step does the database return the actual rows to the user?

A Step 4

B Step 1

C Step 3

D Step 5

💡 Hint

Look at execution_table step 4 where the result set is returned

If the base table 'customers' changes, what happens when you query the view again?

A The view shows old data stored inside it

B The view shows updated data from the base table

C The view query breaks

D The view caches data and does not update

💡 Hint

Remember views run the saved query fresh each time (see key_moments about data storage)

Concept Snapshot

CREATE VIEW view_name AS SELECT ...;
Query the view like a table: SELECT * FROM view_name;
The database runs the saved query behind the scenes.
Views do not store data, only query definitions.
Results reflect current data in base tables.

Full Transcript

A view is like a saved query. When you create a view, you tell the database to remember a query under a name. Later, when you query the view, the database replaces the view name with the saved query and runs it on the base tables. This means the view always shows current data from the base tables, not stored data. For example, creating a view active_customers that selects customers where active=1 lets you query active_customers as if it were a table. Behind the scenes, the database runs the original query and returns the matching rows. This process involves creating the view, storing its query, expanding the view query when used, executing it, and returning the results. Understanding this helps you use views to simplify complex queries and keep your database organized.

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