Message-ID: <gh-pgjdbc-pgjdbc-3930-c3890060988@github.com>
From: "AFulgens (@AFulgens)" <noreply+AFulgens@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 12 Feb 2026 10:34:55 +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: 3890060988
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-3890060988
Content-Type: text/plain; charset=utf-8

I read the issue description and was aware of the semantic problem in the first place.

What I am saying is that in my opinion it's not the JDBC driver's place to correct a wrong done by Sun in 1996/7. (And as we already established in this thread: dates, times, time zones is an excruciatingly difficult topic to solve, and we don't have a very good solution in any of our programming languages as of yet, but the new Java Time API comes close.)

This change, if rolled out without a feature flag, **will** break already existing and working systems just by upgrading the driver version. As it does with 42.7.9.