Join Three Tables: Orders, Users and Payments
Return each order id with the customer's first name and the payment status.
The challenge runs on the SQLabHub practice database (SQLite) and uses the users, orders and payments tables. You can solve it in the browser, with nothing to install.
The task
Get order id, user name and payment status.
A correct answer returns 200 rows with 3 columns: id, first_name, status.
Tables used in this challenge
users 150 rows
id INTEGER (PK) · first_name TEXT · last_name TEXT · email TEXT · phone TEXT · city TEXT · country TEXT · created_at TEXT · status TEXT · is_premium INTEGER
| id | first_name | last_name | phone | city | country | created_at | status | is_premium | |
|---|---|---|---|---|---|---|---|---|---|
orders 200 rows
id INTEGER (PK) · user_id INTEGER · total REAL · discount REAL · item_count INTEGER · status TEXT · order_date TEXT · shipped_date TEXT · shipping_city TEXT · shipping_country TEXT
| id | user_id | total | discount | item_count | status | order_date | shipped_date | shipping_city | shipping_country |
|---|---|---|---|---|---|---|---|---|---|
payments 200 rows
id INTEGER (PK) · order_id INTEGER · user_id INTEGER · amount REAL · method TEXT · status TEXT · paid_at TEXT · transaction_id TEXT
| id | order_id | user_id | amount | method | status | paid_at | transaction_id |
|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| id | first_name | status |
|---|---|---|
First 5 of 200 rows. This is the output of the model solution on the practice database. The task does not fix a sort order, so your rows may come back in a different order.
What you practise
- Choosing exactly which columns a query returns
- Combining rows from two tables on a matching key with an inner join
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
JOIN 3 tables
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
orderstable. - Join
usersonorders.user_id=users.id. - Join
paymentsonorders.id=payments.order_id. - Return only the columns
orders.id,users.first_nameandpayments.status.
Model solution
Checking your session…
What to watch for
Each join adds one table and needs its own ON condition. Payments link to orders by order_id, and an order with several payment records would appear once per payment, so the row count follows the payments table.
- INNER JOIN. An inner join drops rows that have no partner on the other side, and it repeats a row once for every match, which inflates SUM and COUNT.
Related SQL challenges
- Find Orders Whose Payment Amount Differs from the Order TotalSimilar levelMedium
- Find Pairs of Employees in the Same DepartmentSimilar levelMedium
- Select Specific Columns from a TableEasierEasy
- Calculate Profit Generated by Each CustomerHarderHard
- Join Order Items to Products to Show Product NamesSimilar levelMedium
Keep learning
- Lesson: INNER JOIN
- Lesson: The BIG 6 SQL Clauses
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database