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: Tue, 14 Mar 2023 10:03:53 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
The issue with `ZonedDateTime` is that its `ZoneId` might have several variations:
* `ZoneOffset`. In that case, it is pretty much the same thing as `OffsetDateTime`, so we can support it
* `ZoneRegion`. In that case, the zone can have rules regarding DST, however, the database can't really store the zone name, and it applies the current rules. However, it accepts the time zone name, so the DB does not reject timestamps with named zones.
It looks like we might implement `ZonedDateTime` as `ZonedDateTime.toOffsetDateTime()`, so we convert named zones to offsets.
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