pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  

help / color / mirror / Atom feed
From: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3930: Revert semantic calendar changes introduced with #3837
Date: Thu, 05 Feb 2026 16:01:23 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Looks like we should indeed better keep backward compatibility rather than introduce incompatible chainges in patch releases.

```
  The Current Issue

  The fix introduced a semantic breaking change that causes apparent "data corruption" for historical dates (pre-1582):
  ┌────────────────────────────────────────────────┬──────────────────┐
  │                    Scenario                    │      Result      │
  ├────────────────────────────────────────────────┼──────────────────┤
  │ Write 1000-01-02 with 42.7.9, read with 42.7.8 │ Shows 1000-01-07 │
  ├────────────────────────────────────────────────┼──────────────────┤
  │ Write 1000-01-02 with 42.7.8, read with 42.7.9 │ Shows 999-12-28  │
  └────────────────────────────────────────────────┴──────────────────┘


  Possible Resolutions
  ┌──────────────────────────┬───────────────────────────────────────┬──────────────────────────────────────────┐
  │          Option          │                 Pros                  │                   Cons                   │
  ├──────────────────────────┼───────────────────────────────────────┼──────────────────────────────────────────┤
  │ Full revert              │ Restores backward compatibility       │ Keeps the technically incorrect behavior │
  ├──────────────────────────┼───────────────────────────────────────┼──────────────────────────────────────────┤
  │ Major version (43.0.0)   │ Proper semver for breaking change     │ Requires re-release                      │
  ├──────────────────────────┼───────────────────────────────────────┼──────────────────────────────────────────┤
  │ Connection property      │ User choice, both behaviors available │ Added complexity, not clear default      │
  ├──────────────────────────┼───────────────────────────────────────┼──────────────────────────────────────────┤
  │ Default old + opt-in new │ Backward compatible with path forward │ Technical correctness not default        │
  └──────────────────────────┴───────────────────────────────────────┴──────────────────────────────────────────┘
```

I do not see win-win case here :-/

Frankly, I am leaning towards "revert behavior, and add an option that could match driver's behavior with database behavior".

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