Message-ID: <gh-pgjdbc-pgjdbc-1325-c3126898712@github.com>
From: "bokken (@bokken)" <noreply+bokken@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 28 Jul 2025 11:59:24 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #1325: Additional jsr 310 support
In-Reply-To: <gh-pgjdbc-pgjdbc-1325@github.com>
References: <gh-pgjdbc-pgjdbc-1325@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: bokken
X-GitHub-Comment-Id: 3126898712
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 1325
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/1325#issuecomment-3126898712
Content-Type: text/plain; charset=utf-8

Is providing support for (getting) OffsetDateTime and ZonedDateTime by always interpreting as UTC really valuable?
I understand the desire to be liberal in datatype mappings supported, but the lack of actually storing offset and/or time zone make this type lossy.

I think throwing an exception for +/- infinity timestamps is fine.