Message-ID: <gh-pgjdbc-pgjdbc-3930-c3854618446@github.com>
From: "AFulgens (@AFulgens)" <noreply+AFulgens@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 05 Feb 2026 16:07:17 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3930: Revert semantic calendar changes introduced with #3837
In-Reply-To: <gh-pgjdbc-pgjdbc-3930@github.com>
References: <gh-pgjdbc-pgjdbc-3930@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: AFulgens
X-GitHub-Comment-Id: 3854618446
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3930
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3930#issuecomment-3854618446
Content-Type: text/plain; charset=utf-8

This ship has sailed when `java.sql.Date` and `java.sql.Timestamp` has been bound into JDBC and packed with too much magic (throwing no shade on the original authors, time is extremely difficult, and even the new Java time API is not perfect, I sincerely think that it's an unsolvable problem). The "proper" scenario would be a new JDBC API which uses `java.time.OffsetDateTime` as default, but that will never happen.

I think there is no proper solution here on the JDBC-driver level. Clients, who care about semantical correctness, must correct the data _after_ querying it from the `ResultSet`.

Note that if the decision is made for a backroll, it would be nice to notify the MSSQL JDBC team, they currently have an open issue for introducing the same change https://github.com/microsoft/mssql-jdbc/issues/2789 but it's not merged yet.