pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feed[pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone
5+ messages / 2 participants
[nested] [flat]
* [pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone
@ 2026-02-23 08:54 "vlsi (@vlsi)" <[email protected]>
0 siblings, 0 replies; 5+ messages in thread
From: vlsi (@vlsi) @ 2026-02-23 08:54 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Clarifies https://github.com/pgjdbc/pgjdbc/issues/3943
Note: OffsetDateTime UTC behavior is discussed in https://github.com/pgjdbc/pgjdbc/issues/1324.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone
@ 2026-02-23 11:22 ` "davecramer (@davecramer)" <[email protected]>
3 siblings, 0 replies; 5+ messages in thread
From: davecramer (@davecramer) @ 2026-02-23 11:22 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
While the backend does not store the TZ. The timestamp does come back with a TZ if you use timestamptz?
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone
@ 2026-02-23 11:38 ` "vlsi (@vlsi)" <[email protected]>
3 siblings, 0 replies; 5+ messages in thread
From: vlsi (@vlsi) @ 2026-02-23 11:38 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
> The timestamp does come back with a TZ if you use timestamptz
I don't get the question.
---
Well, the backend does send the timezone when using text protocol, and it is discussed in https://github.com/pgjdbc/pgjdbc/issues/1324.
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone
@ 2026-02-23 11:49 ` "davecramer (@davecramer)" <[email protected]>
3 siblings, 0 replies; 5+ messages in thread
From: davecramer (@davecramer) @ 2026-02-23 11:49 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Ah, Ok, so we have an issue when using binary. I think for all other timestamps we just assume the client's timezone, no ?
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone
@ 2026-02-23 12:09 ` "vlsi (@vlsi)" <[email protected]>
3 siblings, 0 replies; 5+ messages in thread
From: vlsi (@vlsi) @ 2026-02-23 12:09 UTC (permalink / raw)
To: pgjdbc/pgjdbc <[email protected]>
Well, `java.sql` types do not have explicit timezone, so we have to convert the value as if it was in "the client's default timezone".
With OffsetDateTime we somehow decided to force UTC, and it causes inconsistency like in #1324.
I think we can use connection timezone when decoding OffsetDateTime, and we can convert UTC binary value into the client's time zone. However, if we ever do so, we should better discuss it in #1324.
This PR just adds extra clarification on the current behavior.
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2026-02-23 12:09 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-02-23 08:54 [pgjdbc/pgjdbc] PR #3944: doc: clarify that OffsetDateTime return UTC time zone as the backend does not store time zone "vlsi (@vlsi)" <[email protected]>
2026-02-23 11:22 ` "davecramer (@davecramer)" <[email protected]>
2026-02-23 11:38 ` "vlsi (@vlsi)" <[email protected]>
2026-02-23 11:49 ` "davecramer (@davecramer)" <[email protected]>
2026-02-23 12:09 ` "vlsi (@vlsi)" <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox