pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed

From: AFulgens (@AFulgens) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3930: Revert semantic calendar changes introduced with #3837
Date: Tue, 10 Feb 2026 15:48:07 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

I provided the code I am using.

I do not convert any string into a date when executing the query, I am effectively doing
```
resultSet.getDate(...).toString()
resultSet.getString(...)
```

And these must not deliver different results, IMO. Cf. [PoLA](https://en.wikipedia.org/wiki/Principle_of_least_astonishment)

Can we at least agree that if I execute the following with `psql`:
```
insert into public.testtable(this_is_a_date) values ('1000-01-01');
```

Then I can expect to get "1000-01-01" regardless of how am I querying the data? (As is the case for the current versions of the MS-SQL, Oracle drivers and for pgjdbc up till 42.7.8)

My argument is that that `java.sql.Date` and `java.sql.Timestamp` have a semantic issue with pre-Gregorian dates is irrelevant at this point and should not be corrected in the **driver code**. If clients have a problem, they have to correct it after querying it. Otherwise any legacy Java code relying on the current behaviour become effectively broken because of this change. Thus, it can be done, but it **must** be in a major release of the driver, if done at all.

view thread (24+ 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 #3930: Revert semantic calendar changes introduced with #3837
  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