Find Customers Who Ordered in 2024
Return the distinct users who placed at least one order during 2024.
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 users who placed orders in 2024.
A correct answer returns 56 rows with one column: user_id.
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
| user_id |
|---|
First 5 of 56 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
- Removing duplicate rows with DISTINCT
- Working with dates in SQLite: strftime, julianday and DATE
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
YEAR filter
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 where the year oforder_dateequals '2024'. - Return only the column
user_id. DISTINCTremoves duplicate rows, so each value appears once.
Model solution
Checking your session…
What to watch for
strftime('%Y', order_date) returns the year as text, so it is compared with the string '2024', not the number. DISTINCT collapses customers who ordered several times that year.
- Date functions. These date functions are SQLite syntax. MySQL uses DATE_FORMAT and DATEDIFF, PostgreSQL uses TO_CHAR, EXTRACT and date subtraction.
- DISTINCT. DISTINCT works on the whole selected row. Adding one more column to the SELECT list can bring the duplicates back.
- 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 Customers with at Least One Order Over 1,000Similar levelMedium
- Find Orders That Took More Than 3 Days to ShipSimilar levelMedium
- List Unique Cities with SELECT DISTINCTEasierEasy
- Find Customers Who Ordered on Consecutive DaysHarderHard
- Find the Second Highest Order Total with LIMIT and OFFSETSimilar levelMedium
Keep learning
- Lesson: Date Functions
- Lesson: SELECT DISTINCT
- Lesson: WHERE Clause
- All SQL practice challenges, by difficulty and topic
- SQL interview questions with answers
- SQL Playground: run any query on the same database