Message-ID: <gh-pgjdbc-pgjdbc-3845-c3431640239@github.com>
From: "victornoel (@victornoel)" <noreply+victornoel@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 22 Oct 2025 10:29:49 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3845: Wrong result on equality between Date and Timestamp given as query parameter
In-Reply-To: <gh-pgjdbc-pgjdbc-3845@github.com>
References: <gh-pgjdbc-pgjdbc-3845@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: victornoel
X-GitHub-Comment-Id: 3431640239
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3845
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3845#issuecomment-3431640239
Content-Type: text/plain; charset=utf-8

> Is it really the case?

At least on Hibernate 5, see the `doBind` methods in https://github.com/hibernate/hibernate-orm/blob/5.6/hibernate-core/src/main/java/org/hibernate/type/descriptor/sql/TimestampTypeDescriptor.java

> Frankly, I think pgjdbc supports java.time for quite some time already, and ORMs should migrate to that API as it is a much cleaner mapping between Java and database types.

Yep, I agree, I will followup with Hibernate on this (for v6+ as v5 is no longer supported)

> They should raise warnings if the application still uses java.sql fields.

Just to be clear, this is even worst: even if the application is not, their code is (at least on v5, again ;)

Great idea with the error-prone ticket!!