N059-M4 Tier 5 · Expert · medium ecommerce · Brightlane

Return each order's `id` and the number of line items recorded against it

Part of Join Fanout and Aggregate Correctness in SQL

The problem

Scenario: Brightlane's operations team is auditing order completeness and needs the line-item count for every order — including orders with no line items recorded against them.

Task: Write a query to return each order's id and the number of line items recorded against it.

Assumptions:

  • Some orders have no recorded line items; those orders must still appear in the result with a count of zero.

Output:

  • One row per order present in the data, including orders with no line items.
  • Columns in this order: order_id, item_count.
Schema · ecommerce 5 tables
categories
id integer
name text
parent_id? integer
products
id integer
name text
category_id integer
price numeric
stock_qty integer
attributes? jsonb
order_items
id integer
order_id integer
product_id integer
quantity integer
unit_price numeric
customers
id integer
name text
email text
city? text
country text
created_at timestamptz
is_active boolean
orders
id integer
customer_id integer
ordered_at timestamptz
status text
total_amount numeric

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first
Solution query
SELECT
  o.id AS order_id,
  COUNT(oi.id) AS item_count
FROM
  orders o
  LEFT JOIN order_items oi ON oi.order_id = o.id
GROUP BY
  o.id

The shape

Some orders have no recorded line items, and the audit needs them to appear with a count of zero rather than drop out entirely. LEFT JOIN keeps every order in the result, and COUNT(oi.id) correctly returns zero for orders whose line-item side is all NULL.

Clause by clause

  • SELECT o.id AS order_id, COUNT(oi.id) AS item_count returns each order's ID and its line-item count. COUNT(oi.id) counts non-null oi.id values inside each group — an order with no line items has only one joined row with oi.id as NULL, so the count is zero.
  • FROM orders o reads every order. This is the side that must be preserved, including the orders with no line items.
  • LEFT JOIN order_items oi ON oi.order_id = o.id attaches matching line items to each order. Orders with no matches still appear in the result, with NULLs filled in for every order_items column.
  • GROUP BY o.id collapses the joined rows down to one per order. Orders with line items get the real count; orders without line items get zero.

Why COUNT(oi.id) and not COUNT(*)

This is the load-bearing distinction for LEFT JOIN counting. COUNT(*) counts every row regardless of NULLs, so an order with no line items — represented in the joined result by one row with NULLs on the order_items side — would be counted as one, not zero. COUNT(oi.id) only counts rows where oi.id is not NULL, which is the correct definition of "has a line item" for this audit.

The trap

Swapping LEFT JOIN for INNER JOIN would drop every line-item-less order from the result entirely, and the audit's whole purpose is to find those orders. The choice between LEFT JOIN and INNER JOIN is set by whether the question needs to see the parents-without-children rows; here it does, so LEFT JOIN is the only shape that fits. Pairing it with COUNT(oi.id) instead of COUNT(*) is the second half of the same decision — the count has to agree with the join about what "no line items" means.

You practiced left-joining the parent table to its children so every parent appears in the result — including parents with zero children, which would drop out of an inner-join shape.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.