Message-ID: <gh-pgjdbc-pgjdbc-3757-c3180678326@github.com>
From: "rlbdv (@rlbdv)" <noreply+rlbdv@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 12 Aug 2025 19:17:19 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3757: PreparedStatement.toString() fails for bytea parameters with at least 42.7.7
In-Reply-To: <gh-pgjdbc-pgjdbc-3757@github.com>
References: <gh-pgjdbc-pgjdbc-3757@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: rlbdv
X-GitHub-Comment-Id: 3180678326
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3757
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3757#issuecomment-3180678326
Content-Type: text/plain; charset=utf-8

Yep, that appears to work just fine, and grepping around I found the related server-prepare.md docs that I suspect none of us had noticed before. It also looks like with a bit of hacking it's possible to extend the relevant libraries (clojure.java.jdbc and next-jdbc) to handle the values in question that way.

Not sure whether we'll do that for now, but glad to know about the option.  Much appreciated.