HAVING clause in MySQL - Time & Space Complexity

Time Complexity: HAVING clause

O(n)

Understanding Time Complexity

When using the HAVING clause in SQL, we want to know how the time to run the query changes as the data grows.

We ask: How does filtering groups after aggregation affect the work the database does?

Scenario Under Consideration

Analyze the time complexity of the following code snippet.

SELECT department, COUNT(*) AS employee_count
FROM employees
GROUP BY department
HAVING COUNT(*) > 10;
    

This query groups employees by department, counts how many are in each, and then keeps only departments with more than 10 employees.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning all employee rows once to group them by department.
• How many times: Once for all rows, then once over each group to apply the HAVING filter.

How Execution Grows With Input

The database reads each employee row once to count them per department. Then it checks each department group to see if it meets the HAVING condition.

Input Size (n)	Approx. Operations
10	About 10 row reads + groups checked
100	About 100 row reads + groups checked
1000	About 1000 row reads + groups checked

Pattern observation: The work grows roughly in direct proportion to the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows linearly as the number of rows increases.

Common Mistake

[X] Wrong: "HAVING filters rows before grouping, so it reduces the work early."

[OK] Correct: HAVING filters after grouping, so the database must first process all rows to form groups before filtering.

Interview Connect

Understanding how HAVING works helps you explain query performance clearly and shows you know how databases handle grouped data.

Self-Check

"What if we replaced HAVING with a WHERE clause before grouping? How would the time complexity change?"

Practice

1. What is the main purpose of the HAVING clause in SQL?

easy

A. To filter groups after aggregation

B. To filter rows before grouping

C. To sort the result set

D. To join two tables

Solution

1. Step 1: Understand filtering in SQL

   The WHERE clause filters rows before grouping, but HAVING filters after groups are formed.

2. Step 2: Identify the role of HAVING

   HAVING is used to filter groups based on aggregate conditions like COUNT or SUM.

3. Final Answer:

   To filter groups after aggregation -> Option A

4. Quick Check:

   HAVING filters groups, not rows [OK]

Hint: HAVING filters groups after aggregation, WHERE filters rows before [OK]

Common Mistakes:

• Confusing HAVING with WHERE clause
• Using HAVING without GROUP BY
• Thinking HAVING sorts data

2. Which of the following is the correct syntax to use HAVING with GROUP BY in MySQL?

easy

A. SELECT col1 FROM table HAVING COUNT(col2) > 5 GROUP BY col1;

B. SELECT col1, COUNT(col2) FROM table GROUP BY col1 HAVING COUNT(col2) > 5;

C. SELECT col1, COUNT(col2) FROM table HAVING COUNT(col2) > 5;

D. SELECT col1, COUNT(col2) FROM table GROUP BY col1 WHERE COUNT(col2) > 5;

Solution

1. Step 1: Recall correct order of clauses

   In SQL, GROUP BY comes before HAVING. The correct order is SELECT -> FROM -> GROUP BY -> HAVING.

2. Step 2: Check each option's syntax

   SELECT col1, COUNT(col2) FROM table GROUP BY col1 HAVING COUNT(col2) > 5; correctly places GROUP BY before HAVING and includes aggregate function in HAVING condition.

3. Final Answer:

   SELECT col1, COUNT(col2) FROM table GROUP BY col1 HAVING COUNT(col2) > 5; -> Option B

4. Quick Check:

   GROUP BY before HAVING [OK]

Hint: GROUP BY must come before HAVING in SQL syntax [OK]

Common Mistakes:

• Placing HAVING before GROUP BY
• Using WHERE with aggregate functions
• Omitting GROUP BY when using HAVING

3. Given the table sales with columns region and amount, what will this query return?

SELECT region, SUM(amount) AS total_sales FROM sales GROUP BY region HAVING total_sales > 1000;

medium

A. All regions with sales less than or equal to 1000

B. Syntax error because alias can't be used in HAVING

C. All regions with total sales greater than 1000

D. Empty result because HAVING filters rows

Solution

1. Step 1: Understand the query logic

   The query groups rows by region and sums amount as total_sales.

2. Step 2: Apply HAVING condition

   It filters groups where total_sales is greater than 1000. Using alias in HAVING is allowed in MySQL.

3. Final Answer:

   All regions with total sales greater than 1000 -> Option C

4. Quick Check:

   HAVING filters groups by aggregate result [OK]

Hint: HAVING filters groups by aggregate values like SUM [OK]

Common Mistakes:

• Thinking HAVING filters rows, not groups
• Assuming alias can't be used in HAVING in MySQL
• Confusing HAVING with WHERE

4. Identify the error in this query:

SELECT department, COUNT(*) FROM employees HAVING COUNT(*) > 10;

medium

A. Missing GROUP BY clause before HAVING

B. COUNT(*) cannot be used in HAVING

C. HAVING should be replaced with WHERE

D. No error, query is correct

Solution

1. Step 1: Check for GROUP BY usage

   The query uses HAVING with COUNT(*) but does not group by department. HAVING requires GROUP BY to define groups.

2. Step 2: Understand HAVING requirements

   HAVING filters groups after aggregation. Without GROUP BY, groups are not defined, causing an error.

3. Final Answer:

   Missing GROUP BY clause before HAVING -> Option A

4. Quick Check:

   HAVING needs GROUP BY to filter groups [OK]

Hint: Always use GROUP BY before HAVING to define groups [OK]

Common Mistakes:

• Using HAVING without GROUP BY
• Replacing HAVING with WHERE incorrectly
• Assuming COUNT(*) can't be in HAVING

5. You have a products table with columns category, price, and stock. Write a query to find categories where the average price is above 50 and total stock is at least 100.
Which query correctly uses HAVING to achieve this?

hard

A. SELECT category FROM products GROUP BY category WHERE AVG(price) > 50 AND SUM(stock) >= 100;

B. SELECT category FROM products HAVING AVG(price) > 50 AND SUM(stock) >= 100 GROUP BY category;

C. SELECT category FROM products WHERE AVG(price) > 50 AND SUM(stock) >= 100 GROUP BY category;

D. SELECT category FROM products GROUP BY category HAVING AVG(price) > 50 AND SUM(stock) >= 100;

Solution

1. Step 1: Recall correct clause order

   The correct order is SELECT -> FROM -> GROUP BY -> HAVING. HAVING filters groups based on aggregate conditions.

2. Step 2: Analyze each option

   SELECT category FROM products GROUP BY category HAVING AVG(price) > 50 AND SUM(stock) >= 100; correctly groups by category and uses HAVING with aggregate functions AVG(price) and SUM(stock).

3. Final Answer:

   SELECT category FROM products GROUP BY category HAVING AVG(price) > 50 AND SUM(stock) >= 100; -> Option D

4. Quick Check:

   HAVING filters grouped data with aggregate conditions [OK]

Hint: Use HAVING after GROUP BY for aggregate filters [OK]

Common Mistakes:

• Placing HAVING before GROUP BY
• Using WHERE with aggregate functions
• Omitting GROUP BY when using HAVING