Find Products in a Price Range with BETWEEN
Return the products priced from 100 to 500.
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 between 100 and 500.
A correct answer returns 23 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 23 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
- Filtering a range of values with BETWEEN
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
Use BETWEEN
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 between 100 and 500, both ends included. - Return every column with
SELECT *.
Model solution
Checking your session…
What to watch for
BETWEEN includes both ends: a product costing exactly 100 or exactly 500 is returned. It is shorthand for price >= 100 AND price <= 500, and the lower bound has to come first.
- BETWEEN. BETWEEN includes both boundary values. On dates stored with a time, the upper bound silently excludes most of the last day.
- WHERE. WHERE is evaluated before the SELECT list, so it cannot use a column alias defined there or the result of an aggregate.
- SELECT *. SELECT * is fine for exploring, but its output changes whenever a column is added to the table. Queries that feed a report should name their columns.
Related SQL challenges
- Compare Two Columns in a WHERE ClauseSimilar levelEasy
- Filter Rows on a Boolean Flag ColumnSimilar levelEasy
- Find Orders That Took More Than 3 Days to ShipHarderMedium
- Filter Rows Where a Column Equals a Text ValueSimilar levelEasy
- Filter Rows After a Given DateSimilar levelEasy
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: BETWEEN
- 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