SQL Timestamp to Date
Drop the time-of-day component from a TIMESTAMP, keeping only the calendar date — a simple, common cast.
What & Why
Casting a TIMESTAMP to DATE (timestamp_column::DATE) discards the time-of-day entirely, keeping only the calendar date. Useful whenever a report needs to group or compare by day, ignoring exactly what time an event happened.
See How It Works
BUSINESS QUESTION
Product wants feedback grouped by calendar date.
| id | user_id | feature_id | rating | nps_score | comment | created_at |
|---|---|---|---|---|---|---|
| 1 | 101 | 1 | 5 | 9 | Clear and useful | 2024-01-25 12:15:00+00 |
| 2 | 102 | 2 | 4 | NULL | Export worked well | 2024-02-20 15:40:00+00 |
| 3 | 103 | 1 | 4 | 7 | Helpful setup flow | 2024-03-18 09:05:00+00 |
| 4 | 104 | 3 | 3 | NULL | Needs clearer timing | 2024-04-08 17:30:00+00 |
EXAMPLE QUERY
SELECT
created_at::date AS feedback_date,
COUNT(*) AS feedback_count
FROM product.feedback
GROUP BY feedback_date
ORDER BY feedback_date;RESULT — exact output from the displayed Queryflo rows
| feedback_date | feedback_count |
|---|---|
| 2024-01-25 | 1 |
| 2024-02-20 | 1 |
| 2024-03-18 | 1 |
| 2024-04-08 | 1 |
Casting creates four actual feedback dates before grouping.
Now You Try
Practice this concept
Product wants feedback grouped by calendar date.
Available schema
productPrefix tables with product.table_name.
feedback_datefeedback_countproduct.feedback| Column | Type |
|---|---|
| id | integer |
| user_id | integer |
| feature_id | integer |
| rating | integer |
| nps_score | integer |
| comment | text |
| created_at | timestamp with time zone |
| moderation_bucket | text |
query.sql
Sign up free to try it on a real business scenario