Top Rated per Category
Find highest rated product in each category.
The challenge runs on the SQLabHub practice database (SQLite) and uses the products and reviews tables. You can solve it in the browser, with nothing to install.
The task
Find highest rated product in each category.
A correct answer returns 10 rows with 12 columns: id, name, category, price, cost, stock, sku, status, rating, review_count, avg_rating, rn.
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 |
|---|---|---|---|---|---|---|---|---|---|
reviews 180 rows
id INTEGER (PK) · product_id INTEGER · user_id INTEGER · rating INTEGER · comment TEXT · reviewed_at TEXT · helpful_votes INTEGER
| id | product_id | user_id | rating | comment | reviewed_at | helpful_votes |
|---|---|---|---|---|---|---|
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 | avg_rating | rn |
|---|---|---|---|---|---|---|---|---|---|---|---|
The complete result: 10 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
- Filtering rows with a WHERE condition
- Summarising many rows into one value with COUNT, SUM, AVG, MIN or MAX
- Grouping rows with GROUP BY to get one result row per group
- Combining rows from two tables on a matching key with an inner join
- Querying the result of another query with a subquery in FROM
- Numbering rows with ROW_NUMBER() to pick one or a few per group
- Restarting a window calculation for each group with PARTITION BY
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
ROW_NUMBER partition
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Build an inner query first (a derived table):
- Read from the
productstable. - Join
reviewsonproducts.id=reviews.product_id. - Group the rows by
products.id, so the result has one row for each value. - For each group, compute
AVG(reviews.rating). - Number the rows with
ROW_NUMBER(), ordered byAVG(reviews.rating)descending, restarting for eachproducts.category.
- Read from the
- Filter in
WHERE: keep the rows wherernequals 1. The filter sits in the outer query because a window function cannot be tested in the WHERE clause of the query that computes it.
Model solution
Checking your session…
What to watch for
- ROW_NUMBER(). ROW_NUMBER() breaks ties arbitrarily. When the ORDER BY inside OVER does not identify one row, the row that gets number 1 can change between runs.
- PARTITION BY. PARTITION BY is not GROUP BY: it keeps every row and only decides which rows a window function looks at.
- Derived table. Columns computed in the inner query are only visible outside under their alias, so every calculated column there needs a name.
Related SQL challenges
- Find the Top 2 Products by Revenue in Each CategorySimilar levelHard
- Find the Top 3 Most Expensive Products in Each CategorySimilar levelHard
- Calculate the Average Review Rating per Product CategoryEasierMedium
- Find the Top-Spending Customer in Each CountrySimilar levelHard
- Find Each Customer's Largest OrderSimilar levelHard
Keep learning
- Lesson: ROW_NUMBER()
- Lesson: Window Functions
- Lesson: SQL Subqueries
- 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