N034-M4 Tier 3 · Intermediate · medium ecommerce · Brightlane

Return the number of days between `'2024-01-01'` and `'2024-12-31'`

Part of Date Arithmetic and Intervals in SQL

The problem

Brightlane's data pipeline validates reporting windows by confirming the number of days in a calendar year.

Write a query to return the number of days between '2024-01-01' and '2024-12-31'.

Output:

  • A single row with one column, days_in_year, containing the day count as a number.
Schema · ecommerce 5 tables
categories
id integer
name text
parent_id? integer
products
id integer
name text
category_id integer
price numeric
stock_qty integer
attributes? jsonb
order_items
id integer
order_id integer
product_id integer
quantity integer
unit_price numeric
customers
id integer
name text
email text
city? text
country text
created_at timestamptz
is_active boolean
orders
id integer
customer_id integer
ordered_at timestamptz
status text
total_amount numeric

Run previews · Check grades

Write a query, then run it to see results here.

Worked solution Try it yourself first
Solution query
SELECT
  '2024-12-31'::date - '2024-01-01'::date AS days_in_year

The shape

DATE - DATE returns an integer day count, and subtracting January 1 from December 31 of the same year returns 365, which matches the day count of a non-leap year. The result is a plain number, suitable for the pipeline's reporting-window check.

Clause by clause

  • SELECT '2024-12-31'::date - '2024-01-01'::date AS days_in_year casts both literals to DATE, subtracts the start of the year from the end, and returns the elapsed days. PostgreSQL counts from one date to the other, exclusive of the start and inclusive of the end. The alias AS days_in_year names the result column.

The trap

365 is the number of days elapsed between January 1 and December 31, not the number of distinct calendar dates in the year. The year 2024 contains 366 distinct dates because it is a leap year, but the subtraction returns 365 because that is how many full days separate the two endpoints. A reader expecting "days in the year" to mean "count of dates that fall in the year" would read this result as off by one. The two questions are different. DATE - DATE answers the elapsed-days question. Counting distinct dates in a range needs a different construction.

You practiced date - date over a full calendar year — the result reflects elapsed days from start to end, not a count of distinct dates spanned.

How you actually get good at SQL

Reading explains SQL. Writing it, over and over with instant feedback, is what makes you fluent.

That's the whole SQLMaxx loop: 600+ real problems, instant AI feedback, mastery you can actually see, and spaced review that won't let you forget.

A stack of SQL practice problem cards, the top card showing an employees table.
615 problems · 66 concepts

Real problems. Not toy examples.

615 hand-built problems spanning all 66 concepts, from basic SELECTs to window functions, built on real schemas and real business questions, the kind you'll actually get asked on the job. Enough reps to make SQL automatic.

A retro computer showing a SQL query marked correct with a green checkmark.
Instant AI feedback

Write a query. Know if it's right in one second.

No copying an answer and hoping it clicked. The AI grader checks your real query against real data, catches exactly what's wrong, and explains the fix in plain English, like a senior analyst reading over your shoulder on every problem.

A circular mastery progress dial filling from blue to green, the SQLMaxx diamond at its center.
Mastery tracking

Stop guessing whether you actually know it.

SQLMaxx tracks every concept and shows you what you've mastered and what's still shaky. Your skills fill in one concept at a time, so 'I think I get joins' becomes something you can prove.

A SQL query editor circled by a blue return arrow with a clock, scheduled to come back for review.
Spaced review

Learn it once. Keep it for good.

Most of what you learn this week fades by next week. So when a concept comes due for review, SQLMaxx hands you a fresh problem to solve from a blank editor, not a flashcard to re-read. A research-backed spaced-repetition algorithm (FSRS) times each return for right before you'd forget, so your SQL is still there months later, when the interview or the job actually needs it.

Practice, feedback, mastery, review. That's the loop that turns reading into real skill.

Start free

No account, no credit card. Start solving in under a minute.