pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #1325: Additional jsr 310 support
Date: Mon, 28 Jul 2025 12:11:20 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
>Is providing support for (getting) OffsetDateTime and ZonedDateTime by always interpreting as UTC really valuable?
1) `OffsetDateTime` has been implemented in https://github.com/pgjdbc/pgjdbc/pull/2467, and I believe it is way better that all the `java.util.Date`, `java.sql.Timestamp`, `java.util.Calendar` alternatives. Sure PostgreSQL loses user-provided zone, however, we can't overcome it.
2) Both `OffsetDateTime`, `ZonedDateTime`, and `Instant` represent a moment-in-time, which maps nicely to `timestamptz`. It is quite useful for working with `timestamptz`.
Of course, it would be nice if PostgreSQL could store timezone as a text-like region name, however, that feature is not available in the backend yet. If they ever improve `timestamptz` we could revise our `ZonedDateTime` mapping.
view thread (25+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: github://pgjdbc/pgjdbc
Cc: [email protected], [email protected]
Subject: Re: [pgjdbc/pgjdbc] issue #1325: Additional jsr 310 support
In-Reply-To: <<[email protected]>>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox