devanbenz commented on issue #12218: URL: https://github.com/apache/datafusion/issues/12218#issuecomment-2324818646
> I wouldn't say that timestamp has UTC time. timestamp is local date/time. You can think of it as a struct with fields year/month/day/hour/minute/seconds(fractional) and it has no relationship with UTC. However, when doing math on timestamp values using a date/time library it's often to represent it as UTC-based. Makes sense, so the expectation is for the date-time calculation to be correct for that TZ but no offset? So for the example above: ``` > select (now() AT TIME ZONE 'America/Denver')::timestamp; +----------------------------+ | now() | +----------------------------+ | 2024-08-28T17:08:20.042920 | +----------------------------+ ``` Should actually be: ``` > select (now() AT TIME ZONE 'America/Denver')::timestamp; +----------------------------+ | now() | +----------------------------+ | 2024-08-28T11:08:13.578025 | +----------------------------+ ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
