Subqueries vs JOINs comparison in MySQL - Visual Side-by-Side Comparison

Concept Flow - Subqueries vs JOINs comparison

Start Query

↓

Evaluate Subquery or JOIN

↓

Subquery: Execute inner query first

↓

Get subquery result

↓

Use result in outer query

↓

JOIN: Combine tables row by row

↓

Filter and select columns

↓

Return combined result

↓

End Query

This flow shows how a query with subqueries first runs the inner query and then uses its result, while a JOIN combines tables directly before filtering and returning results.

Execution Sample

MySQL

SELECT e.name, d.department_name
FROM employees e
JOIN departments d ON e.department_id = d.id;

This query joins employees with their departments to list employee names with their department names.

Execution Table

Step	Action	Evaluation	Result
1	Start query execution	N/A	Ready to process tables
2	Read employees table row 1	e.name='Alice', e.department_id=1	Row data loaded
3	Find matching department with d.id=1	d.department_name='HR'	Match found
4	Combine employee and department data	('Alice', 'HR')	Row added to result
5	Read employees table row 2	e.name='Bob', e.department_id=2	Row data loaded
6	Find matching department with d.id=2	d.department_name='Sales'	Match found
7	Combine employee and department data	('Bob', 'Sales')	Row added to result
8	No more employee rows	End of employees table	Query complete

💡 All employee rows processed and matched with departments, query ends.

Variable Tracker

Variable	Start	After 1	After 2	Final
e.name	N/A	Alice	Bob	Bob
e.department_id	N/A	1	2	2
d.department_name	N/A	HR	Sales	Sales
Result Rows	Empty	('Alice', 'HR')	('Alice', 'HR'), ('Bob', 'Sales')	('Alice', 'HR'), ('Bob', 'Sales')

Key Moments - 2 Insights

Why does the JOIN combine rows from both tables instead of running one query inside another?

JOIN works by matching rows from both tables directly, combining them in one step (see execution_table rows 2-7), unlike subqueries which run separately first.

How does the query know which department matches each employee?

The ON condition e.department_id = d.id filters rows to match employee's department_id with department's id, shown in execution_table rows 3 and 6.

Visual Quiz - 3 Questions

Look at the execution_table, what is the combined row after processing the first employee?

A ('Alice', 'HR')

B ('Bob', 'Sales')

C ('Alice', 'Sales')

D ('Bob', 'HR')

💡 Hint

Check row 4 in execution_table where the first combined row is added.

At which step does the query finish processing all employee rows?

A Step 6

B Step 8

C Step 4

D Step 2

💡 Hint

Look at the exit_note and last row in execution_table.

If the JOIN condition was removed, what would happen to the result rows?

A Only employees with matching departments appear

B No rows would be returned

C All combinations of employees and departments appear (Cartesian product)

D Query would error out

💡 Hint

Without ON condition, JOIN returns every possible pair of rows from both tables.

Concept Snapshot

JOIN combines rows from two tables based on a condition.
Subqueries run inner queries first and use results in outer queries.
JOIN is often faster and clearer for related tables.
Subqueries can be simpler for filtering but may be slower.
Use JOIN to combine data side-by-side.
Use subqueries to filter or compute before main query.

Full Transcript

This visual execution compares subqueries and JOINs in MySQL. The flow shows that subqueries run inner queries first, then use results in the outer query, while JOINs combine tables row by row directly. The example query joins employees with departments using a matching condition. Step-by-step, each employee row is matched with a department row, combined, and added to the result. Variables track employee names, department ids, and combined results. Key moments clarify how JOIN matches rows and why it differs from subqueries. The quiz tests understanding of combined rows, query completion, and effects of removing the JOIN condition. The snapshot summarizes when to use JOINs or subqueries for combining or filtering data.

Practice

1. Which of the following best describes the main difference between a JOIN and a subquery in MySQL?

easy

A. JOIN runs inside another query; subqueries combine tables side-by-side.

B. JOIN is used only for filtering; subqueries are used only for combining tables.

C. JOIN combines tables side-by-side; subqueries run inside another query to filter or find values.

D. JOIN and subqueries are exactly the same in functionality and performance.

Solution

1. Step 1: Understand the role of JOIN

   A JOIN combines rows from two or more tables side-by-side based on a related column between them.

2. Step 2: Understand the role of subqueries

   A subquery is a query nested inside another query, often used to filter or find specific values before the main query runs.

3. Final Answer:

   JOIN combines tables side-by-side; subqueries run inside another query to filter or find values. -> Option C

4. Quick Check:

   JOIN = combine tables, Subquery = nested query [OK]

Hint: JOINs combine tables; subqueries nest queries inside [OK]

Common Mistakes:

• Confusing JOINs as nested queries
• Thinking subqueries combine tables side-by-side
• Believing JOINs and subqueries have identical performance always

2. Which of the following is the correct syntax to write a JOIN between tables employees and departments on the column department_id?

easy

A. SELECT * FROM employees JOIN departments USING employees.department_id;

B. SELECT * FROM employees JOIN departments WHERE employees.department_id = departments.department_id;

C. SELECT * FROM employees, departments ON employees.department_id = departments.department_id;

D. SELECT * FROM employees JOIN departments ON employees.department_id = departments.department_id;

Solution

1. Step 1: Identify correct JOIN syntax

   The correct JOIN syntax uses the ON keyword to specify the matching columns between tables.

2. Step 2: Check each option

   SELECT * FROM employees JOIN departments ON employees.department_id = departments.department_id; uses ON correctly. SELECT * FROM employees JOIN departments WHERE employees.department_id = departments.department_id; incorrectly uses WHERE instead of ON. SELECT * FROM employees, departments ON employees.department_id = departments.department_id; uses comma join but incorrectly adds ON. SELECT * FROM employees JOIN departments USING employees.department_id; misuses USING with full column name.

3. Final Answer:

   SELECT * FROM employees JOIN departments ON employees.department_id = departments.department_id; -> Option D

4. Quick Check:

   JOIN requires ON for matching columns [OK]

Hint: Use ON to specify join condition, not WHERE [OK]

Common Mistakes:

• Using WHERE instead of ON for JOIN condition
• Using comma join with ON clause
• Incorrect USING syntax with full column names

3. Given the tables orders(order_id, customer_id, amount) and customers(customer_id, name), what will the following query return?

SELECT name FROM customers WHERE customer_id IN (SELECT customer_id FROM orders WHERE amount > 100);

medium

A. Names of customers who have orders with amount greater than 100.

B. All customer names regardless of orders.

C. Names of customers who have no orders.

D. Syntax error due to subquery.

Solution

1. Step 1: Analyze the subquery

   The subquery selects customer_id from orders where amount is greater than 100.

2. Step 2: Analyze the main query

   The main query selects names from customers where customer_id is in the list returned by the subquery.

3. Final Answer:

   Names of customers who have orders with amount greater than 100. -> Option A

4. Quick Check:

   Subquery filters customers by order amount [OK]

Hint: IN with subquery filters matching rows [OK]

Common Mistakes:

• Assuming all customers are returned
• Thinking it returns customers without orders
• Believing subquery causes syntax error

4. Identify the error in the following query that tries to list all employees with their department names:

SELECT e.name, d.department_name FROM employees e JOIN departments d WHERE e.department_id = d.department_id;

medium

A. Using WHERE instead of HAVING for join condition.

B. Missing ON keyword before the join condition.

C. Incorrect table aliases used.

D. No error; query is correct.

Solution

1. Step 1: Check JOIN syntax

   JOIN requires the ON keyword to specify the join condition between tables.

2. Step 2: Identify the mistake

   The query uses WHERE instead of ON to specify the join condition, which is incorrect syntax.

3. Final Answer:

   Missing ON keyword before the join condition. -> Option B

4. Quick Check:

   JOIN needs ON, not WHERE, for conditions [OK]

Hint: JOIN conditions must use ON, not WHERE [OK]

Common Mistakes:

• Using WHERE instead of ON for JOIN
• Confusing HAVING with JOIN condition
• Assuming aliases cause error

5. You want to find all customers who have placed orders but only want to use a JOIN instead of a subquery. Which query correctly replaces this subquery?

SELECT name FROM customers WHERE customer_id IN (SELECT customer_id FROM orders);

hard

A. SELECT DISTINCT c.name FROM customers c JOIN orders o ON c.customer_id = o.customer_id;

B. SELECT c.name FROM customers c JOIN orders o WHERE c.customer_id = o.customer_id;

C. SELECT c.name FROM customers c, orders o WHERE c.customer_id = o.customer_id;

D. SELECT name FROM customers LEFT JOIN orders ON customer_id = customer_id;

Solution

1. Step 1: Understand the original subquery

   The subquery selects customer_ids from orders, filtering customers who placed orders.

2. Step 2: Translate to JOIN

   Using JOIN on customer_id between customers and orders returns matching customers. DISTINCT is needed to avoid duplicates.

3. Step 3: Evaluate options

   SELECT DISTINCT c.name FROM customers c JOIN orders o ON c.customer_id = o.customer_id; uses JOIN with ON and DISTINCT correctly. SELECT c.name FROM customers c JOIN orders o WHERE c.customer_id = o.customer_id; misses ON keyword. SELECT c.name FROM customers c, orders o WHERE c.customer_id = o.customer_id; uses old-style join but is valid but may return duplicates. SELECT name FROM customers LEFT JOIN orders ON customer_id = customer_id; uses LEFT JOIN but ON condition is ambiguous.

4. Final Answer:

   SELECT DISTINCT c.name FROM customers c JOIN orders o ON c.customer_id = o.customer_id; -> Option A

5. Quick Check:

   JOIN with ON and DISTINCT matches subquery result [OK]

Hint: Use JOIN with ON and DISTINCT to replace IN subquery [OK]

Common Mistakes:

• Omitting ON keyword in JOIN
• Not using DISTINCT causing duplicates
• Using ambiguous ON conditions