Message-ID: <gh-pgjdbc-pgjdbc-3482-c2599279306@github.com>
From: "BbIKTOP (@BbIKTOP)" <noreply+BbIKTOP@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Fri, 17 Jan 2025 21:56:00 +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: 2599279306
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-2599279306
Content-Type: text/plain; charset=utf-8

as bindings have their type, it could be propagated inside nested blocks, as it done for ordinary queries. So, the problem is this propagation.
I see explicit cast could be done the Postgres ':type' way, which is not portable, or by binding each parameter explicitly, to prevent the necessity of the type propagation. I am currently working on the second, which, as I stated, a bit complicated because query is generated and I am trying to imagine how to get the type info from the source. I probably need to store some 'metadata' or something. Maybe pl block could help but I'm worrying about performance - this app should process a lot of data as fast as possible.