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

Return the order ID, product name, and quantity for every line item on record

Part of Joining Multiple Tables in SQL

The problem

Brightlane's product team wants to see each order line item alongside the name of the product it represents.

Write a query to return the order ID, product name, and quantity for every line item on record.

Output:

  • One row per order line item, with columns order_id, product_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,
  p.name AS product_name,
  oi.quantity
FROM
  orders o
  JOIN order_items oi ON o.id = oi.order_id
  JOIN products p ON oi.product_id = p.id

The shape

The chain pivots through order_items, the junction table — each line item connects on one side to its order and on the other to its product. Two JOINs on shared keys land the result at one row per line item with the product's name attached.

Clause by clause

  • SELECT o.id AS order_id, p.name AS product_name, oi.quantity picks one column from each table. p.name is the product name; o.id is the order ID. Without the aliases, both names would be ambiguous — every table in the schema has an id, and both products and others have a name.
  • FROM orders o anchors the chain on orders.
  • JOIN order_items oi ON o.id = oi.order_id attaches the line items. This is the multiplying step: an order with three line items becomes three rows in the intermediate result.
  • JOIN products p ON oi.product_id = p.id then resolves each line item to its product. Each line item points at exactly one product, so this join enriches the rows without multiplying them further. The row count is settled by the order_items join above.

You practiced a three-table chain through a junction (order_items) to its two parent tables. The recurring shape: junctions almost always connect to multiple dimensions, so they're frequently the middle node in a multi-table join.

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.