Message-ID: <gh-pgjdbc-pgjdbc-3365-c2607795078@github.com>
From: "ecki (@ecki)" <noreply+ecki@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 22 Jan 2025 17:05:46 +0000
Subject: Re: [pgjdbc/pgjdbc] issue #3365: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
In-Reply-To: <gh-pgjdbc-pgjdbc-3365@github.com>
References: <gh-pgjdbc-pgjdbc-3365@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: ecki
X-GitHub-Comment-Id: 2607795078
X-GitHub-Comment-Type: issue_comment
X-GitHub-Edited-At: 2025-01-22T19:29:03Z
X-GitHub-Issue: 3365
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3365#issuecomment-2607795078
Content-Type: text/plain; charset=utf-8

BTW here is an example where MSJDBC has implemented tostring for (better) JPA Slow-execution logging (which also uses `PS#toString()`, at least in hibernate case)

https://github.com/microsoft/mssql-jdbc/issues/2086

So it’s a reasonable expectation that tostring is used, should not corrupt the Parameters and allows at least a rough idea what Statement is (keep ? Placeholders is Fine) in question (it doesnt make a stable Cache key function Mandates, though, but thats not what the bug is about).