Message-ID: <gh-pgjdbc-pgjdbc-3365-c2312759366@github.com>
From: "MrEasy (@MrEasy)" <noreply+MrEasy@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 27 Aug 2024 14:40:13 +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: MrEasy
X-GitHub-Comment-Id: 2312759366
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3365
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/issues/3365#issuecomment-2312759366
Content-Type: text/plain; charset=utf-8

Thanks for the input rg. the cache - yes will look into it.
But it's just an example, basically any developer might decide to call #toString on an object - for whatever reason, could be some debugging code, printing it to log - so should not fail of course.