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

Return each customer's `id`, name, and `customer_status` — set to `'Active'` if they have placed at least one order and `'Inactive'` otherwise

Part of NULL Propagation in Complex Queries in SQL

The problem

Scenario: Brightlane's CRM team is preparing a re-engagement campaign and needs every customer classified as 'Active' (has placed at least one order) or 'Inactive' (has placed none).

Task: Write a query to return each customer's id, name, and customer_status — set to 'Active' if they have placed at least one order and 'Inactive' otherwise.

Assumptions:

  • A customer's customer_status is 'Active' when at least one order is on record for them and 'Inactive' when none is on record.
  • The result covers every customer.

Output:

  • One row per customer.
  • Columns in this order: customer_id, customer_name, customer_status.
  • Sorted by customer_name ascending.
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
  c.id AS customer_id,
  c.name AS customer_name,
  CASE
    WHEN COUNT(o.id) > 0 THEN 'Active'
    ELSE 'Inactive'
  END AS customer_status
FROM
  customers c
  LEFT JOIN orders o ON o.customer_id = c.id
GROUP BY
  c.id,
  c.name
ORDER BY
  c.name

The shape

COUNT(o.id) returns the number of matched orders per customer, and a CASE expression over that count labels each customer 'Active' or 'Inactive'. The LEFT JOIN is what makes the count reach zero for customers with no orders — without it, those customers would be dropped before the count step ran.

Clause by clause

  • SELECT c.id AS customer_id, c.name AS customer_name, CASE WHEN COUNT(o.id) > 0 THEN 'Active' ELSE 'Inactive' END AS customer_status returns each customer's id and name alongside the status label. The CASE evaluates the count once the group has been formed; a customer with at least one matched order gets 'Active', and a customer whose COUNT(o.id) is 0 falls through to 'Inactive'.
  • FROM customers c LEFT JOIN orders o ON o.customer_id = c.id pairs each customer with their orders. The LEFT JOIN preserves customers who have none; for those customers, o.id is NULL.
  • GROUP BY c.id, c.name collapses the customer-and-orders rows back to one row per customer.
  • ORDER BY c.name sorts the report alphabetically by customer name.

Why this and not COUNT(*) > 0

COUNT(*) counts rows regardless of whether the right side of the LEFT JOIN matched. For a customer with no orders, the LEFT JOIN still emits one placeholder row with every orders column set to NULL, and COUNT(*) would count it as 1. Every customer would arrive at the CASE with a count of at least one, so every customer would be labeled 'Active' and the 'Inactive' branch would never fire. COUNT(o.id) ignores NULL values, which means the placeholder row contributes nothing — the orderless customer's count lands on 0 and the 'Inactive' branch fires.

You practiced classifying parents by whether they have any matching children — translating a count-based existence check into a categorical label per customer.

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.