What if missing data could be grouped and sorted without extra hassle?
Why NULL in DISTINCT, GROUP BY, and ORDER BY in SQL? - Purpose & Use Cases
Imagine you have a list of customer orders on paper, and some orders have missing information like no delivery date. You try to group or sort these orders by delivery date manually, but the missing dates confuse you.
Manually handling missing data is slow and confusing. You might treat missing dates as different each time or forget to group them properly. This leads to mistakes and wasted time.
SQL treats NULL values in a special way when using DISTINCT, GROUP BY, and ORDER BY. It groups all missing values together and sorts them consistently, so you don't have to guess or do extra work.
Check each row for missing dates and group manually
SELECT DISTINCT delivery_date FROM orders; -- NULLs grouped automatically
This lets you easily find unique values, group data, and sort results even when some data is missing, making your queries accurate and simple.
A store manager wants to see all unique delivery dates including orders without a date, grouped together to plan shipments efficiently.
NULL values represent missing data in SQL.
SQL groups all NULLs together in DISTINCT and GROUP BY.
ORDER BY places NULLs consistently for clear sorting.
Practice
NULL values when using DISTINCT in SQL?Solution
Step 1: Understand DISTINCT behavior with NULL
In SQL,DISTINCTtreats allNULLvalues as equal, grouping them together.Step 2: Result of DISTINCT on NULL values
This means only oneNULLappears in the output, no matter how manyNULLs exist.Final Answer:
All NULL values are treated as one group and appear once. -> Option BQuick Check:
NULLs grouped once = A [OK]
- Thinking NULLs are ignored in DISTINCT
- Assuming each NULL is unique
- Believing DISTINCT errors on NULL
employees on column department?Solution
Step 1: Identify correct DISTINCT syntax
The correct SQL syntax to get unique values isSELECT DISTINCT column FROM table;. Parentheses are not used with DISTINCT.Step 2: Check each option
SELECT DISTINCT department FROM employees; uses correct syntax. SELECT UNIQUE department FROM employees; uses UNIQUE which is not standard SQL. SELECT DISTINCT(department) FROM employees; incorrectly uses parentheses. SELECT department DISTINCT FROM employees; has wrong keyword order.Final Answer:
SELECT DISTINCT department FROM employees; -> Option DQuick Check:
Standard DISTINCT syntax = D [OK]
- Using UNIQUE instead of DISTINCT
- Adding parentheses after DISTINCT
- Misplacing DISTINCT keyword
sales with column region containing values: ('East', 'West', NULL, 'East', NULL), what will be the result of this query?SELECT region FROM sales GROUP BY region ORDER BY region ASC;
Solution
Step 1: GROUP BY groups NULLs together
The GROUP BY groups all NULL values as one group. So NULL appears once.Step 2: ORDER BY ascending places NULL first
In ascending order, NULL values come before any text values. Then 'East' and 'West' follow alphabetically.Final Answer:
[NULL, 'East', 'West'] -> Option AQuick Check:
NULL first in ORDER BY ASC = A [OK]
- Assuming NULL sorts last
- Treating NULL as a string value
- Expecting multiple NULL rows in GROUP BY
category values including NULLs?SELECT category FROM products GROUP BY category ORDER BY category;
Solution
Step 1: Check syntax and logic
The query groups by category and orders by category. This is valid SQL syntax.Step 2: Understand NULL handling
GROUP BY includes NULL as a group, so NULL values appear once. ORDER BY sorts NULLs first by default.Final Answer:
Query is correct and will work as intended. -> Option AQuick Check:
GROUP BY with ORDER BY and NULLs works = C [OK]
- Thinking NULLs are excluded by GROUP BY
- Believing ORDER BY can't follow GROUP BY
- Assuming missing semicolon breaks query
orders with a column status that can be 'Pending', 'Shipped', or NULL. You want to count how many orders exist for each status, including NULLs as a separate group. Which query correctly achieves this?Solution
Step 1: Understand grouping with NULL
GROUP BY status groups NULL values as one group, so counting includes NULLs separately.Step 2: Analyze each option
SELECT status, COUNT(*) FROM orders GROUP BY status ORDER BY status ASC; groups all statuses including NULL and orders them ascending. SELECT status, COUNT(*) FROM orders GROUP BY status HAVING status IS NOT NULL ORDER BY status; excludes NULL with HAVING. SELECT status, COUNT(*) FROM orders WHERE status IS NOT NULL GROUP BY status ORDER BY status; filters NULL out in WHERE. SELECT DISTINCT status, COUNT(*) FROM orders ORDER BY status; uses DISTINCT with COUNT(*) incorrectly.Final Answer:
SELECT status, COUNT(*) FROM orders GROUP BY status ORDER BY status ASC; -> Option CQuick Check:
GROUP BY includes NULL groups = B [OK]
- Filtering NULLs out before grouping
- Using HAVING to exclude NULLs unintentionally
- Misusing DISTINCT with aggregate functions
Ready to prove it?
Pass the test and this pattern moves unknown
