Filter Rows After a Given Date
Return the users whose account was created after 1 January 2023.
The challenge runs on the SQLabHub practice database (SQLite) and uses the users table. You can solve it in the browser, with nothing to install.
The task
Find users created after 2023-01-01.
A correct answer returns 54 rows with 10 columns: id, first_name, last_name, email, phone, city, country, created_at, status, is_premium.
Tables used in this challenge
users 150 rows
id INTEGER (PK) · first_name TEXT · last_name TEXT · email TEXT · phone TEXT · city TEXT · country TEXT · created_at TEXT · status TEXT · is_premium INTEGER
| id | first_name | last_name | phone | city | country | created_at | status | is_premium | |
|---|---|---|---|---|---|---|---|---|---|
The first rows of each table are shown. See how all the tables relate on the database schema page.
Expected output
| id | first_name | last_name | phone | city | country | created_at | status | is_premium | |
|---|---|---|---|---|---|---|---|---|---|
First 5 of 54 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
Hint and approach
Try the challenge first. Open these only when you need them.
Show the hint
Use WHERE date
Show the step-by-step approach
How the model solution is built, in the order the database evaluates it:
- Read from the
userstable. - Filter in
WHERE: keep the rows wherecreated_atis greater than '2023-01-01'. - Return every column with
SELECT *.
Model solution
Checking your session…
What to watch for
Dates in this database are TEXT in YYYY-MM-DD form, so string comparison sorts them correctly. The same comparison on 01/02/2023-style text would be wrong. Using > excludes the boundary day itself.
- 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
- Filter Rows Where a Column Equals a Text ValueSimilar levelEasy
- Filter Rows on a Boolean Flag ColumnSimilar levelEasy
- Find Orders That Took More Than 3 Days to ShipHarderMedium
- Find Employees Earning More Than 50,000Similar levelEasy
- Compare Two Columns in a WHERE ClauseSimilar levelEasy
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- 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