Calculate the Average Value per Item of Each Order
Return every order with its total divided by its item count, highest value per item first.
The challenge runs on the SQLabHub practice database (SQLite) and uses the orders table. You can solve it in the browser, with nothing to install.
The task
Find orders with highest value per item.
A correct answer returns 200 rows with 11 columns: id, user_id, total, discount, item_count, status, order_date, shipped_date, shipping_city, shipping_country, density.
Tables used in this challenge
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 | density |
|---|---|---|---|---|---|---|---|---|---|---|
First 5 of 200 rows. This is the output of the model solution on the practice database.
What you practise
- Sorting the result with ORDER BY
- Deriving a new column from an expression and naming it with an alias
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
total / item_count
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
orderstable. - Add the calculated column
density:total * 1.0 / item_count. - Sort the result by
densitydescending.
Model solution
Checking your session…
What to watch for
Dividing two integers in SQLite truncates the result, which is why total is multiplied by 1.0 first. Here total is already REAL, so the factor is a safeguard; with two integer columns it changes the answer.
- Calculated columns. Dividing one integer by another truncates the result in SQLite. Multiply one side by 1.0 to get decimals.
- ORDER BY. Without ORDER BY the row order is not guaranteed, even if it looks stable. Rows that tie on the sort columns can come back in any order.
Related SQL challenges
- Sort Products by Profit Margin (Price Minus Cost)Similar levelHard
- Calculate Rating Variance per Product Without a VARIANCE FunctionSimilar levelHard
- Count Orders by Status with GROUP BYEasierEasy
- Calculate Employee Tenure in Days and Sort by LongestSimilar levelHard
- Calculate Average Items per Order for Each CustomerSimilar levelHard
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: Comments & Aliases
- Lesson: ORDER BY
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database