Price Above Category Avg
Find products priced above their category average.
The challenge runs on the SQLabHub practice database (SQLite) and uses the products table. You can solve it in the browser, with nothing to install.
The task
Find products priced above their category average.
A correct answer returns 63 rows with 10 columns: id, name, category, price, cost, stock, sku, status, rating, review_count.
Tables used in this challenge
products 120 rows
id INTEGER (PK) · name TEXT · category TEXT · price REAL · cost REAL · stock INTEGER · sku TEXT · status TEXT · rating REAL · review_count INTEGER
| id | name | category | price | cost | stock | sku | status | rating | review_count |
|---|---|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| id | name | category | price | cost | stock | sku | status | rating | review_count |
|---|---|---|---|---|---|---|---|---|---|
First 5 of 63 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
- Writing a subquery that refers to the current row of the outer query
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
Correlated subquery
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
productstable. - Filter in
WHERE: keep the rows wherepriceis greater than the value returned by a subquery. - The subquery is correlated: it refers to the current outer row, so it is evaluated for each row. It works like this:
- Read from the
productstable. - Filter in
WHERE: keep the rows wherecategoryequals the outer row'scategory. - Aggregate over all the rows that are left: compute
AVG(price). 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
- Correlated subquery. A correlated subquery is evaluated per outer row, which gets slow on large tables. A join to a grouped subquery or a window function usually does the same work in one pass.
- 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 More Than Their Department AverageSimilar levelMedium
- Find the Highest-Paid Employee in Each DepartmentSimilar levelMedium
- Compare Two Columns in a WHERE ClauseEasierEasy
- Find Products with No Sales in the Last Month of DataHarderHard
- Find the Amount of Each Customer's Most Recent OrderSimilar levelMedium
Keep learning
- Lesson: Correlated 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