Message-ID: <gh-pgjdbc-pgjdbc-3845-c3431451590@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 22 Oct 2025 09:53:03 +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: vlsi
X-GitHub-Comment-Id: 3431451590
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-3431451590
Content-Type: text/plain; charset=utf-8

`Oid.DATE`, `Oid.TIMESTAMP`, and `Oid.TIMESTAMPTZ` differ.
At the same time, it is hard to tell if `.setTimestamp` means `TIMESTAMP` or `TIMESTAMPTZ`.

I'm not sure if it is the only reason for going with `UNSPECIFIED` when sending the dates to the backend, however, it looks like the primary way of moving forward should be `java.time` types.

Is there anything stopping you from using `java.time` with Hibernate?