Message-ID: <gh-pgjdbc-pgjdbc-3924-c3891012780@github.com>
From: "damixd1 (@damixd1)" <noreply+damixd1@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 12 Feb 2026 13:36:37 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3924: 0001-01-01 Date not properly saved in database and not properly red from database
In-Reply-To: <gh-pgjdbc-pgjdbc-3924@github.com>
References: <gh-pgjdbc-pgjdbc-3924@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: damixd1
X-GitHub-Comment-Id: 3891012780
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3924
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3924#issuecomment-3891012780
Content-Type: text/plain; charset=utf-8

@davecramer I do not think this is a good idea to close this issue, while problem still exits and was caused by https://github.com/pgjdbc/pgjdbc/pull/3887 
"get/set Object with LocalDate.class works" - that would require changes in all libraries that use those methods, for example Hibernate. I do not think this is a way to go.

In my opinion, https://github.com/pgjdbc/pgjdbc/pull/3887 should be reverted at least, and then problem fixed comprehensively later.