GROUP BY with NULL values behavior in SQL - Time & Space Complexity

Time Complexity: GROUP BY with NULL values behavior

O(n)

Understanding Time Complexity

When using GROUP BY in SQL, it groups rows based on column values, including NULLs.

We want to understand how the time to group grows as the number of rows increases, especially with NULL values.

Scenario Under Consideration

Analyze the time complexity of this SQL query:

SELECT department, COUNT(*)
FROM employees
GROUP BY department;
    

This query groups employees by their department, counting how many are in each. Some departments may be NULL.

Identify Repeating Operations

Look at what repeats as the query runs:

• Primary operation: Scanning each row to find its department value.
• How many times: Once for every row in the employees table.

How Execution Grows With Input

As the number of rows grows, the query must check each one to group it.

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

Pattern observation: The work grows directly with the number of rows.

Final Time Complexity

Time Complexity: O(n)

This means the time to group grows in a straight line with the number of rows.

Common Mistake

[X] Wrong: "NULL values cause the query to run slower because they need special handling in GROUP BY."

[OK] Correct: NULLs are treated as a regular group value, so they don't add extra time beyond scanning rows.

Interview Connect

Understanding how grouping scales helps you explain query performance clearly and confidently.

Self-Check

What if we added an ORDER BY after GROUP BY? How would that affect the time complexity?

Practice

1. What happens to NULL values when you use GROUP BY on a column containing them?

easy

A. All NULL values are grouped together as one group.

B. NULL values are ignored and not included in any group.

C. Each NULL value forms its own separate group.

D. GROUP BY causes an error if NULL values exist.

Solution

1. Step 1: Understand how GROUP BY handles NULLs

   In SQL, GROUP BY treats all NULL values in a column as equal, grouping them into one group.

2. Step 2: Confirm behavior with example

   If a column has multiple rows with NULL, they appear as a single group in the result.

3. Final Answer:

   All NULL values are grouped together as one group. -> Option A

4. Quick Check:

   GROUP BY NULL = one group [OK]

Hint: Remember: NULLs group together, not separately [OK]

Common Mistakes:

• Thinking NULLs are ignored in GROUP BY
• Assuming each NULL is a separate group
• Believing GROUP BY errors on NULL values

2. Which of the following SQL queries correctly groups rows by a column that may contain NULL values?

easy

A. SELECT category, COUNT(*) FROM products GROUP BY category;

B. SELECT category, COUNT(*) FROM products GROUP BY category WHERE category IS NOT NULL;

C. SELECT category, COUNT(*) FROM products WHERE category IS NOT NULL GROUP BY category;

D. SELECT category, COUNT(*) FROM products GROUP BY category HAVING category IS NOT NULL;

Solution

1. Step 1: Check GROUP BY syntax with NULLs

   SELECT category, COUNT(*) FROM products GROUP BY category; uses correct syntax: grouping by category including NULLs. GROUP BY works with NULL values without extra filters.

2. Step 2: Analyze other options

   Options A and D misuse WHERE and HAVING clauses with GROUP BY. SELECT category, COUNT(*) FROM products WHERE category IS NOT NULL GROUP BY category; filters out NULLs before grouping, which is valid but excludes NULL groups.

3. Final Answer:

   SELECT category, COUNT(*) FROM products GROUP BY category; -> Option A

4. Quick Check:

   GROUP BY with NULLs needs no special filter [OK]

Hint: GROUP BY works directly with NULLs, no WHERE needed [OK]

Common Mistakes:

• Using WHERE after GROUP BY (syntax error)
• Filtering NULLs before grouping unintentionally
• Misusing HAVING clause for filtering NULLs

3. Given the table sales with data:

product | region
-------|--------
A      | East
B      | NULL
A      | NULL
B      | East
NULL   | West
NULL   | NULL

What is the result of:

SELECT region, COUNT(*) FROM sales GROUP BY region ORDER BY region;

medium

A. [
{"region": "East", "count": 2},
{"region": "NULL", "count": 3},
{"region": "West", "count": 1}
]

B. [
{"region": "East", "count": 2},
{"region": "NULL", "count": 2},
{"region": "West", "count": 1}
]

C. [
{"region": "East", "count": 2},
{"region": null, "count": 2},
{"region": "West", "count": 1}
]

D. [
{"region": null, "count": 3},
{"region": "East", "count": 2},
{"region": "West", "count": 1}
]

Solution

1. Step 1: Group rows by region including NULLs

   Rows with region 'East' = 2, 'West' = 1, and NULL values (3 rows) are grouped together as one NULL group.

2. Step 2: Understand NULL display and count

   SQL returns NULL as null (not string 'NULL'). Count for NULL group is 3 because three rows have region NULL. ORDER BY region ASC places null first.

3. Final Answer:

   [{"region": null, "count": 3}, {"region": "East", "count": 2}, {"region": "West", "count": 1}] -> Option D

4. Quick Check:

   GROUP BY NULL groups count 3, NULL shown as null [OK]

Hint: NULLs group together and show as null, not 'NULL' string [OK]

Common Mistakes:

• Counting NULL rows separately
• Displaying NULL as string 'NULL'
• Miscounting NULL group size

4. Consider this query:

SELECT department, COUNT(*) FROM employees GROUP BY department;

It returns an error. Which fix will correctly handle NULL values in department to avoid errors?

medium

A. Add WHERE department IS NOT NULL before GROUP BY.

B. No fix needed; GROUP BY never errors on NULL.

C. Use HAVING department IS NOT NULL after GROUP BY.

D. Replace NULL with a string using COALESCE(department, 'Unknown') in SELECT and GROUP BY.

Solution

1. Step 1: Understand why no error occurs

   In standard SQL, GROUP BY handles NULL values correctly by grouping all NULLs together into one group. No error is thrown.

2. Step 2: Confirm no fix needed

   The query runs successfully and includes a NULL group in the results.

3. Final Answer:

   No fix needed; GROUP BY never errors on NULL. -> Option B

4. Quick Check:

   GROUP BY NULL = no error [OK]

Hint: GROUP BY handles NULLs without error [OK]

Common Mistakes:

• Thinking GROUP BY errors on NULLs
• Unnecessarily filtering out NULLs with WHERE
• Misusing HAVING for pre-group filtering

5. You have a table orders with columns customer_id and status, where status can be NULL. You want to count orders by status, treating all NULL statuses as 'Pending'. Which query correctly achieves this?

hard

A. SELECT status, COUNT(*) FROM orders GROUP BY status WHERE status IS NULL;

B. SELECT status, COUNT(*) FROM orders GROUP BY status HAVING status IS NOT NULL;

C. SELECT COALESCE(status, 'Pending') AS order_status, COUNT(*) FROM orders GROUP BY order_status;

D. SELECT status, COUNT(*) FROM orders GROUP BY status ORDER BY status;

Solution

1. Step 1: Replace NULL with 'Pending' using COALESCE

   COALESCE(status, 'Pending') converts NULL statuses to 'Pending' for counting.

2. Step 2: Group by the alias used in SELECT

   Grouping by order_status ensures all NULLs are counted under 'Pending'.

3. Final Answer:

   SELECT COALESCE(status, 'Pending') AS order_status, COUNT(*) FROM orders GROUP BY order_status; -> Option C

4. Quick Check:

   COALESCE + GROUP BY alias counts NULL as 'Pending' [OK]

Hint: Use COALESCE and group by alias to count NULLs as desired [OK]

Common Mistakes:

• Filtering out NULLs instead of replacing them
• Using WHERE after GROUP BY (syntax error)
• Grouping by original column without COALESCE