HAVING clause in MySQL - Step-by-Step Execution

Concept Flow - HAVING clause

Start with a table

↓

GROUP BY groups rows

↓

Aggregate functions calculate

↓

HAVING filters groups

↓

Return filtered groups

The HAVING clause filters groups created by GROUP BY after aggregation, unlike WHERE which filters rows before grouping.

Execution Sample

MySQL

SELECT department, COUNT(*) AS emp_count
FROM employees
GROUP BY department
HAVING emp_count > 2;

This query counts employees per department and returns only departments with more than 2 employees.

Execution Table

Step	Action	Intermediate Result	HAVING Condition Check	Output
1	Group rows by department	Groups: Sales(3), HR(2), IT(4)	N/A	No output yet
2	Calculate COUNT(*) for each group	Sales=3, HR=2, IT=4	N/A	No output yet
3	Apply HAVING emp_count > 2	Check Sales: 3 > 2	True	Include Sales
4	Apply HAVING emp_count > 2	Check HR: 2 > 2	False	Exclude HR
5	Apply HAVING emp_count > 2	Check IT: 4 > 2	True	Include IT
6	Return filtered groups	Sales and IT groups	N/A	Output rows for Sales and IT

💡 All groups checked; only those with emp_count > 2 are returned

Variable Tracker

Variable	Start	After Grouping	After Aggregation	After HAVING Filter
groups	empty	Sales(3), HR(2), IT(4)	Sales=3, HR=2, IT=4	Sales=3, IT=4
emp_count	N/A	N/A	3, 2, 4	3, 4

Key Moments - 2 Insights

Why doesn't HAVING filter individual rows like WHERE?

HAVING works after grouping and aggregation, filtering groups, not individual rows. See execution_table rows 1-3 where grouping and aggregation happen before HAVING filters.

Can HAVING use column names not in GROUP BY?

Yes, HAVING can use aggregate results like emp_count which are not in GROUP BY. This is shown in execution_table row 3 where emp_count is used in HAVING.

Visual Quiz - 3 Questions

Look at the execution_table, which department is excluded by the HAVING clause?

A HR

B IT

C Sales

D None

💡 Hint

Check the HAVING Condition Check column in rows 4 and 5

At which step are the groups created?

A Step 2

B Step 3

C Step 1

D Step 6

💡 Hint

Look at the Action column describing grouping

If the HAVING condition changed to emp_count > 3, which groups would be included?

A Sales and IT

B Only IT

C Only Sales

D All groups

💡 Hint

Refer to emp_count values in variable_tracker after aggregation

Concept Snapshot

HAVING clause filters groups after aggregation
Used with GROUP BY to restrict grouped results
Syntax: SELECT ... GROUP BY ... HAVING condition
HAVING can use aggregate functions like COUNT(), SUM()
Different from WHERE which filters rows before grouping

Full Transcript

The HAVING clause is used in SQL to filter groups created by the GROUP BY clause. First, rows are grouped by a column, then aggregate functions like COUNT calculate values per group. HAVING applies a condition to these aggregated values to decide which groups to keep. Unlike WHERE, which filters individual rows before grouping, HAVING filters after grouping. For example, a query can count employees per department and use HAVING to show only departments with more than two employees. The execution steps show grouping, aggregation, then filtering by HAVING. Variables track groups and counts before and after filtering. Common confusions include why HAVING filters groups not rows, and that HAVING can use aggregate results. Visual quiz questions help reinforce these ideas by referencing the execution steps and variable changes.