Message-ID: <gh-pgjdbc-pgjdbc-3845-c3611098209@github.com>
From: "m-van-tilburg (@m-van-tilburg)" <noreply+m-van-tilburg@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 04 Dec 2025 09:32:52 +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: m-van-tilburg
X-GitHub-Comment-Id: 3611098209
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-3611098209
Content-Type: text/plain; charset=utf-8

> Nothing, the problem is Hibernate itself, it's implementing the use of those types by converting them to `java.sql.Timestamp` before calling `setTimestamp` on the statement :)

Are you aware that recent Hibernate versions have a setting to control this behavior? See [JAVA_TIME_USE_DIRECT_JDBC](https://docs.hibernate.org/orm/7.2/javadocs/org/hibernate/cfg/MappingSettings.html#JAVA_TIME_USE_DIRECT_JDBC)