GROUP BY clause in MySQL - Time & Space Complexity

Time Complexity: GROUP BY clause

O(n)

Understanding Time Complexity

When using the GROUP BY clause in SQL, it's important to know how the time to run the query changes as the data grows.

We want to understand how grouping rows affects 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;
    

This query counts how many employees are in each department by grouping rows with the same department.

Identify Repeating Operations

Identify the loops, recursion, array traversals that repeat.

• Primary operation: Scanning all rows in the employees table once.
• How many times: Once for each row in the table.

How Execution Grows With Input

As the number of employees grows, the database must look at each row to group them.

Input Size (n)	Approx. Operations
10	About 10 row checks
100	About 100 row checks
1000	About 1000 row checks

Pattern observation: The work grows directly with the number of rows; doubling rows roughly doubles the work.

Final Time Complexity

Time Complexity: O(n)

This means the time to run the query grows in a straight line with the number of rows in the table.

Common Mistake

[X] Wrong: "GROUP BY makes the query run much slower because it does extra work for each group."

[OK] Correct: The main work is scanning all rows once; grouping just organizes them as it goes, so the time mostly depends on total rows, not groups.

Interview Connect

Understanding how grouping affects query time helps you explain database behavior clearly and shows you know how data size impacts performance.

Self-Check

"What if we added an ORDER BY clause after GROUP BY? How would the time complexity change?"

Practice

1. What is the main purpose of the GROUP BY clause in a MySQL query?

easy

A. To filter rows based on a condition

B. To sort the result set in ascending order

C. To join two or more tables together

D. To group rows that have the same values in specified columns

Solution

1. Step 1: Understand the role of GROUP BY

   The GROUP BY clause groups rows that share the same values in one or more columns.

2. Step 2: Differentiate from other clauses

   Sorting is done by ORDER BY, filtering by WHERE, and joining by JOIN. GROUP BY is specifically for grouping rows.

3. Final Answer:

   To group rows that have the same values in specified columns -> Option D

4. Quick Check:

   GROUP BY = group rows by column values [OK]

Hint: GROUP BY groups rows by column values [OK]

Common Mistakes:

• Confusing GROUP BY with ORDER BY
• Using GROUP BY to filter rows
• Thinking GROUP BY joins tables

2. Which of the following is the correct syntax to group rows by the column department in a MySQL query?

easy

A. SELECT * FROM employees GROUP BY department;

B. SELECT * FROM employees GROUP department BY;

C. SELECT * FROM employees ORDER BY department GROUP;

D. SELECT * FROM employees WHERE department GROUP BY;

Solution

1. Step 1: Recall correct GROUP BY syntax

   The correct syntax is: SELECT columns FROM table GROUP BY column_name;

2. Step 2: Check each option

   SELECT * FROM employees GROUP BY department; matches the correct syntax exactly. Others have misplaced keywords or wrong order.

3. Final Answer:

   SELECT * FROM employees GROUP BY department; -> Option A

4. Quick Check:

   GROUP BY column_name syntax = SELECT * FROM employees GROUP BY department; [OK]

Hint: GROUP BY follows SELECT ... FROM ... GROUP BY column [OK]

Common Mistakes:

• Placing GROUP BY after WHERE clause incorrectly
• Swapping GROUP BY and ORDER BY keywords
• Using GROUP BY without specifying columns

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

SELECT region, SUM(amount) FROM sales GROUP BY region;

medium

A. Total sales amount for each region

B. List of all sales amounts without grouping

C. Syntax error due to missing alias

D. Average sales amount for each region

Solution

1. Step 1: Understand the query components

   The query groups rows by region and sums the amount for each group.

2. Step 2: Interpret the result

   It returns one row per region with the total sales amount summed up.

3. Final Answer:

   Total sales amount for each region -> Option A

4. Quick Check:

   GROUP BY + SUM = total per group [OK]

Hint: SUM with GROUP BY gives total per group [OK]

Common Mistakes:

• Thinking it returns average instead of sum
• Expecting all rows without grouping
• Assuming syntax error without alias

4. Identify the error in this query:

SELECT department, COUNT(employee_id) FROM employees WHERE salary > 50000 GROUP BY employee_id;

medium

A. COUNT cannot be used with employee_id

B. GROUP BY should use department, not employee_id

C. WHERE clause cannot be used with GROUP BY

D. Missing ORDER BY clause

Solution

1. Step 1: Analyze GROUP BY usage

   The query groups by employee_id but selects department, which causes mismatch.

2. Step 2: Correct grouping column

   To count employees per department, GROUP BY should be on department, matching the selected column.

3. Final Answer:

   GROUP BY should use department, not employee_id -> Option B

4. Quick Check:

   GROUP BY column must match selected non-aggregated columns [OK]

Hint: GROUP BY columns must match selected non-aggregated columns [OK]

Common Mistakes:

• Grouping by wrong column not in SELECT
• Thinking WHERE conflicts with GROUP BY
• Assuming ORDER BY is mandatory

5. You have a products table with columns category, price, and stock. Which query correctly finds the average price and total stock for each category?

hard

A. SELECT category, AVG(price), SUM(stock) FROM products GROUP BY price;

B. SELECT category, price, stock FROM products GROUP BY category;

C. SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category;

D. SELECT category, AVG(price), SUM(stock) FROM products;

Solution

1. Step 1: Identify aggregation needs

   We want average price and total stock per category, so use AVG(price) and SUM(stock).

2. Step 2: Group by category

   To get results per category, GROUP BY category is required.

3. Step 3: Check each option

   SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category; correctly uses GROUP BY category with AVG and SUM. Others miss grouping or group by wrong column.

4. Final Answer:

   SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category; -> Option C

5. Quick Check:

   Aggregate functions + GROUP BY category = SELECT category, AVG(price), SUM(stock) FROM products GROUP BY category; [OK]

Hint: Use GROUP BY category with AVG and SUM for correct aggregation [OK]

Common Mistakes:

• Grouping by wrong column like price
• Not using GROUP BY with aggregate functions
• Selecting columns without aggregation or grouping