findepi commented on issue #5827:
URL: https://github.com/apache/arrow-rs/issues/5827#issuecomment-2349137830
> There currently is a misalignment with how casting from
`Timestamp('time/zone') -> Timestamp(None)` functions. There is an expectation
that this cast should effectively "retain" the timezone, for example:
>
> `2033-05-18T08:33:20+01:00` -> `2033-05-18T08:33:20`
from SQL spec perspective. this is "the correct way" .
> the way Postgres does this is "more correct"
BTW I've been heavily involved in timestamp-related work in the Trino
project. Timestamps is one of very few cases where following PostgreSQL is not
the right thing, because PostgreSQL misses real support for zones:
_For timestamp with time zone, the internally stored value is always in UTC
(Universal Coordinated Time, traditionally known as Greenwich Mean Time, GMT).
An input value that has an explicit time zone specified is converted to UTC
using the appropriate offset for that time zone._[^1]
[^1]: https://www.postgresql.org/docs/current/datatype-datetime.html
--
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]
