From: | Thomas Kellerer <spam_eater(at)gmx(dot)net> |
---|---|
To: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Java 8 OffsetDateTime clarification |
Date: | 2019-05-07 06:11:03 |
Message-ID: | qar7ho$4rfr$1@blaine.gmane.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
David Wall schrieb am 07.05.2019 um 04:31:
> This seems incorrect to me.
> The backend, when using TIMESTAMP WITH TIME ZONE, stores the date+time+tzoffset
No, it does not.
From https://www.postgresql.org/docs/current/datatype-datetime.html
> 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. If no time zone is stated in the input string, then it is
> assumed to be in the time zone indicated by the system's TimeZone
> parameter, and is converted to UTC using the offset for the timezone
> zone.
>
> When a timestamp with time zone value is output, it is always
> converted from UTC to the current timezone zone, and displayed as
> local time in that zone
From | Date | Subject | |
---|---|---|---|
Next Message | David Wall | 2019-05-07 16:03:05 | Re: Java 8 OffsetDateTime clarification |
Previous Message | David Wall | 2019-05-07 02:31:52 | Java 8 OffsetDateTime clarification |