N018-M4 Tier 2 · Core SQL · medium ecommerce · Brightlane

Return the product name for every product that has never appeared on any order line

Part of LEFT JOIN and RIGHT JOIN in SQL

The problem

Brightlane's inventory team is reviewing which catalogue items have never moved.

Write a query to return the product name for every product that has never appeared on any order line.

Assumptions:

  • The products table contains every product in the catalogue.
  • The order_items table contains one row per product per order; product_id links each line item back to a product.
  • A product that has never moved is one whose id does not appear in order_items.product_id.

Output:

  • One row per never-sold product, with a single column product_name.
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
  p.name AS product_name
FROM
  products p
  LEFT JOIN order_items oi ON p.id = oi.product_id
WHERE
  oi.order_id IS NULL

The shape

The LEFT JOIN from products to order_items keeps every product; the WHERE oi.order_id IS NULL filter then keeps only the products whose line-item columns came back as NULL — meaning the product never appeared on any order line. The 33 rows in the result are exactly the never-sold catalogue items.

Clause by clause

  • SELECT p.name AS product_name returns just the product name from the left side — that's all the inventory team needs to identify the items.
  • FROM products p LEFT JOIN order_items oi ON p.id = oi.product_id pairs each product with each of the order lines that reference it. Products that have sold appear once per line item with real values in oi.*. Products that have never sold appear once with NULL in every oi.* column.
  • WHERE oi.order_id IS NULL keeps only the unmatched products. order_items.order_id is part of the junction table's identity — every real line item has both an order and a product. So oi.order_id IS NULL is the unmatched signal: the join synthesised a NULL row to preserve a product that has no line item anywhere.

Why this and not INNER JOIN

INNER JOIN would return only product-line pairs that exist — every product that has sold at least once. The never-sold products would silently disappear before any filter could pick them out. The inventory question is the opposite of what INNER JOIN returns, and the shape that surfaces the absence is LEFT JOIN plus IS NULL on the right side.

The trap

With a junction table on the right, the trap is checking NULL on the wrong column. WHERE oi.product_id IS NULL works on this query because every right-side column is NULL for unmatched rows. But oi.product_id is the column being joined on — if the schema allowed product_id to be NULL on a real row (a defective record, an orphan), the filter would conflate two different facts: "the row was synthesised by the outer join" and "the row exists but has a missing product reference." Checking a primary-key-style column (oi.order_id in this junction table, or a true primary key when there is one) keeps the unmatched-by-outer-join signal clean.

You practiced the anti-join against a junction table. The same LEFT JOIN ... WHERE right.key IS NULL shape applies — the only thing that changes is which side of the join you anchor on (the dimension you want to enumerate, in this case products).

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.