Orders with High Item Count
Find orders with item count above average.
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 item count above average.
A correct answer returns 105 rows with 10 columns: id, user_id, total, discount, item_count, status, order_date, shipped_date, shipping_city, shipping_country.
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 |
|---|---|---|---|---|---|---|---|---|---|
First 5 of 105 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
- Returning every column of a table with SELECT *
- Filtering rows with a WHERE condition
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Using the result of one query inside another
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
AVG(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. - Filter in
WHERE: keep the rows whereitem_countis greater than the value returned by a subquery. - The subquery runs once and returns a single value. It works like this:
- Read from the
orderstable. - Aggregate over all the rows that are left: compute
AVG(item_count). With no GROUP BY, the result is a single row.
- Read from the
- Return every column with
SELECT *.
Model solution
Checking your session…
What to watch for
- Subquery. A subquery compared with =, > or < must return exactly one row and one column. If it can return several rows, use IN or an aggregate.
- Aggregate functions. Aggregates skip NULLs. AVG divides by the number of non-NULL values and COUNT(column) can be smaller than COUNT(*).
- WHERE. WHERE is evaluated before the SELECT list, so it cannot use a column alias defined there or the result of an aggregate.
Related SQL challenges
- Find Employees Earning Above the Company AverageSimilar levelMedium
- Find Orders from the Last 30 Days of DataSimilar levelMedium
- Find Unshipped Orders with IS NULLEasierEasy
- Find Employees Earning Above the Median SalaryHarderHard
- Count Orders per User in the Latest Year of DataSimilar levelMedium
Keep learning
- Lesson: SQL Subqueries
- Lesson: Aggregate Functions
- Lesson: WHERE Clause
- 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