Message-ID: <gh-pgjdbc-pgjdbc-3757-c3175787244@github.com>
From: "rlbdv (@rlbdv)" <noreply+rlbdv@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 11 Aug 2025 16:27:35 +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: 3175787244
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-3175787244
Content-Type: text/plain; charset=utf-8

Oh, *of course*.

And just to be sure it's clear, previously, PGobjects with type "bytea" and values of "\xHEX" did work, (PuppetDB has relied on that in various places). Though did pgjdbc actually intend to support that?

In any case, if support is desirable now, then I think I understand what you're suggesting, and I'll likely pursue it. Although you may have to bear with me -- my Java is somewhat rusty.