Message-ID: <gh-pgjdbc-pgjdbc-3482-c2599705013@github.com>
From: "BbIKTOP (@BbIKTOP)" <noreply+BbIKTOP@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Sat, 18 Jan 2025 12:51:26 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3482: When using java.sql.Timestamp for update, an exception thrown
In-Reply-To: <gh-pgjdbc-pgjdbc-3482@github.com>
References: <gh-pgjdbc-pgjdbc-3482@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: BbIKTOP
X-GitHub-Comment-Id: 2599705013
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3482
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3482#issuecomment-2599705013
Content-Type: text/plain; charset=utf-8

Unfortunately. This "upsert" requires _one constraint_. In my case, generated queries could contain more than one and condition could be just condition, on the column without constraints. As it is generated, program actually knows little about merge conditions. So, will stay with direct bindings, looks like in this case type information isn't lost and query is working. Thank you! Probably the last question - where could I ask about fixing? I understand that there's almost no chances, but anyways. pgsql-hackers?