Find Orders That Took More Than 3 Days to Ship
Return the orders where more than three days passed between ordering and shipping.
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 orders where shipping took more than 3 days.
A correct answer returns 65 rows with 10 columns: id, user_id, total, discount, item_count, status, order_date, shipped_date, shipping_city, shipping_country.
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
| id | user_id | total | discount | item_count | status | order_date | shipped_date | shipping_city | shipping_country |
|---|---|---|---|---|---|---|---|---|---|
First 5 of 65 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
- 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
Use julianday
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 number of days fromorder_datetoshipped_dateis greater than 3. - Return every column with
SELECT *.
Model solution
Checking your session…
What to watch for
julianday() turns a date into a day number, so subtracting two of them gives days. Unshipped orders have a NULL difference and drop out. In this practice dataset shipped_date is random and sometimes earlier than order_date, so the pattern is real but the delays are not.
- Date functions. These date functions are SQLite syntax. MySQL uses DATE_FORMAT and DATEDIFF, PostgreSQL uses TO_CHAR, EXTRACT and date subtraction.
- 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
- Find Customers Who Ordered in 2024Similar levelMedium
- Build a Monthly Revenue Report Excluding Cancelled OrdersSimilar levelMedium
- Filter Rows After a Given DateEasierEasy
- Count Orders in Each Customer's First 7 DaysHarderHard
- Filter Rows on a Boolean Flag ColumnEasierEasy
Same technique, other tables
More practice on this pattern with different columns:
Keep learning
- Lesson: Date 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