Count Distinct Products Bought by Each Customer
Return each user with the number of different products they have ordered, most varied first.
The challenge runs on the SQLabHub practice database (SQLite) and uses the orders and order_items tables. You can solve it in the browser, with nothing to install.
The task
Find users who ordered the highest number of distinct products.
A correct answer returns 114 rows with 2 columns: user_id, diversity.
Tables used in this challenge
orders 200 rows
id INTEGER (PK) · user_id INTEGER · total REAL · discount REAL · item_count INTEGER · status TEXT · order_date TEXT · shipped_date TEXT · shipping_city TEXT · shipping_country TEXT
| id | user_id | total | discount | item_count | status | order_date | shipped_date | shipping_city | shipping_country |
|---|---|---|---|---|---|---|---|---|---|
order_items 496 rows
id INTEGER (PK) · order_id INTEGER · product_id INTEGER · quantity INTEGER · unit_price REAL · subtotal REAL
| id | order_id | product_id | quantity | unit_price | subtotal |
|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| user_id | diversity |
|---|---|
First 5 of 114 rows. This is the output of the model solution on the practice database.
What you practise
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Counting different values with COUNT(DISTINCT …)
- Grouping rows with GROUP BY to get one result row per group
- Combining rows from two tables on a matching key with an inner join
- Sorting the result with ORDER BY
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
COUNT DISTINCT product_id
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
orderstable. - Join
order_itemsonorders.id=order_items.order_id. - Group the rows by
orders.user_id, so the result has one row for each value. - For each group, compute
COUNT(DISTINCT order_items.product_id), which counts each different value once. - Sort the result by
diversitydescending.
Model solution
Checking your session…
What to watch for
The path is orders to order_items. A customer who bought the same product in three orders has three joined rows but one distinct product, which is why the count needs DISTINCT.
- INNER JOIN. An inner join drops rows that have no partner on the other side, and it repeats a row once for every match, which inflates SUM and COUNT.
- COUNT(DISTINCT). After a join, COUNT(*) counts joined rows. Counting the parent entity needs COUNT(DISTINCT its id).
- GROUP BY. Every selected column must either be in GROUP BY or sit inside an aggregate. SQLite accepts other columns and returns an arbitrary value for them; most databases raise an error.
Related SQL challenges
- Calculate Average Items per Order for Each CustomerSimilar levelHard
- Calculate Profit Generated by Each CustomerSimilar levelHard
- Calculate Revenue and Units Sold per Product CategoryEasierMedium
- Count Distinct Products per OrderEasierMedium
- Find Orders Containing More Than One ProductEasierMedium
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: INNER JOIN
- Lesson: Aggregate Functions
- Lesson: GROUP BY
- Lesson: ORDER BY
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database