You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TIMESTAMP WITH TIME ZONE and TIMESTAMPTZ theoretically are the same on Postgresql (1), but they are not for other dialects like Oracle(2) (that doesn't support TIMESTAMPTZ). Therefore, we should parse EXACTLY the same timestamp info as input and output, instead of losing its conversion.
The standard only supports TIMESTAMP WITH TIMEZONE(3)
TIMESTAMP WITH TIME ZONE
andTIMESTAMPTZ
theoretically are the same on Postgresql (1), but they are not for other dialects likeOracle
(2) (that doesn't supportTIMESTAMPTZ
). Therefore, we should parse EXACTLY the same timestamp info as input and output, instead of losing its conversion.The standard only supports
TIMESTAMP WITH TIMEZONE
(3)This applies to
TIME
as well.[1] : https://www.postgresql.org/docs/current/datatype-datetime.html
[2] : https://docs.oracle.com/en/database/oracle/oracle-database/12.2/nlspg/datetime-data-types-and-time-zone-support.html#GUID-3F1C388E-C651-43D5-ADBC-1A49E5C2CA05
[3] : https://jakewheat.github.io/sql-overview/sql-2016-foundation-grammar.html#datetime-type
Fixes: #589
The text was updated successfully, but these errors were encountered: