Orders with Full User Info
Retrieve orders with all user details.
The challenge runs on the SQLabHub practice database (SQLite) and uses the users and orders tables. You can solve it in the browser, with nothing to install.
The task
Retrieve orders with all user details.
A correct answer returns 200 rows with 20 columns: id, user_id, total, discount, item_count, status, order_date, shipped_date, shipping_city, shipping_country, id, first_name, last_name, email, phone, city, country, created_at, status, is_premium.
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 |
|---|---|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| id | user_id | total | discount | item_count | status | order_date | shipped_date | shipping_city | shipping_country | id | first_name | last_name | phone | city | country | created_at | status | is_premium | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
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
- 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 users
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.
Model solution
Checking your session…
What to watch for
- 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
- Join Order Items to Products to Show Product NamesSimilar levelMedium
- Join Three Tables: Orders, Users and PaymentsSimilar levelMedium
- Calculate Profit Generated by Each CustomerHarderHard
- Calculate the Average Review Rating per Product CategorySimilar levelMedium
- Find Orders Whose Payment Amount Differs from the Order TotalSimilar levelMedium
Keep learning
- Lesson: INNER JOIN
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database