N022-E1 Tier 2 · Core SQL · easy ecommerce · Brightlane

Return the order ID, customer name, and quantity for every order line

Part of Joining Multiple Tables in SQL

The problem

Brightlane's sales team needs a line-item report showing each order alongside the customer who placed it and the quantity of each item in that order.

Write a query to return the order ID, customer name, and quantity for every order line.

Assumptions:

  • The result row count is one row per order line item (not one row per order).

Output:

  • One row per order line, with columns order_id, customer_name, and quantity.
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,
  c.name AS customer_name,
  oi.quantity
FROM
  orders o
  JOIN customers c ON o.customer_id = c.id
  JOIN order_items oi ON o.id = oi.order_id

The shape

Two JOINs chain three tables on shared keys — orders to customers by customer_id, then orders to order_items by order_id. The result lands at one row per line item, because order_items is the most-multiplying table in the chain.

Clause by clause

  • SELECT o.id AS order_id, c.name AS customer_name, oi.quantity picks one column from each of the three tables. Every reference is alias-prefixed, which is the only way the bare names id and name stay unambiguous in a chain where both orders and customers have a column called id.
  • FROM orders o anchors the chain on orders and aliases the table as o.
  • JOIN customers c ON o.customer_id = c.id attaches the customer to each order through the foreign key. Each order has one customer, so this join doesn't change the row count.
  • JOIN order_items oi ON o.id = oi.order_id then attaches every line item belonging to that order. This is the multiplying step — an order with three items becomes three rows. The first row pair for Alice Nguyen's order 1 shows two rows because that order has two line items.

You practiced chaining three tables in a single FROM clause with two JOIN clauses. The recurring shape: each JOIN adds one table; the ON clause specifies how that new table connects to the working set so far.

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.