SQLMaxx
Sign in Start free
N032-M3 Tier 3 · Intermediate · medium ecommerce · Brightlane

Return the string `'2024-06-15 09:30:00+05:30'` cast as a timezone-aware timestamp

Part of Date and Time Types in PostgreSQL in SQL

The problem

A Brightlane regional warehouse logged an inventory event at 09:30 Indian Standard Time (UTC+05:30) on 2024-06-15. The engineering team needs the moment recorded as a timezone-aware timestamp.

Write a query to return the string '2024-06-15 09:30:00+05:30' cast as a timezone-aware timestamp.

Output:

  • A single row with one column, ist_event, typed as a timezone-aware timestamp.
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
Check answerShift Ctrl ↵

Run previews · Check grades

Write a query, then run it to see results here.
Worked solution Try it yourself first
Solution query
SELECT
  '2024-06-15 09:30:00+05:30'::TIMESTAMPTZ AS ist_event

The shape

The +05:30 inside the literal tells PostgreSQL that the wall-clock reading is in Indian Standard Time, and the ::timestamptz cast triggers the UTC conversion at parse time. The stored value is the absolute moment that 09:30 IST corresponds to, which is 04:00 UTC.

Clause by clause

  • SELECT '2024-06-15 09:30:00+05:30'::timestamptz AS ist_event evaluates the literal once and returns it as a TIMESTAMPTZ. PostgreSQL reads 09:30 as the wall clock and +05:30 as the offset, subtracts the offset to land on UTC, and stores 2024-06-15 04:00:00+00 internally. The displayed value depends on the session zone; the stored value is fixed.
  • There is no FROM because no table is being read.

Why the explicit ::timestamptz cast

The +05:30 in the string is what lets PostgreSQL compute the absolute moment, but the destination type still has to be declared. Without ::timestamptz, the literal resolves as text and the offset is preserved only as characters in a string. The downstream system would not know that 09:30+05:30 is the same moment as 04:00+00. The cast is what turns the offset from a visible character into a load-bearing fact about the value.

The trap

'2024-06-15 09:30:00'::timestamptz (no offset in the literal) would also produce a TIMESTAMPTZ, but PostgreSQL would assume the session's current time zone for the conversion. The same query would produce a different absolute moment when run from a session set to a different zone. The IST offset has to live inside the literal, where it is documented and load-bearing, not inferred from whatever session happens to run the query.

You practiced casting a non-UTC offset literal to TIMESTAMPTZ — PostgreSQL converts the value to UTC at write time using the literal's offset.

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.