Message-ID: <gh-pgjdbc-pgjdbc-3369-c2740473222@github.com>
From: "MrEasy (@MrEasy)" <noreply+MrEasy@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 20 Mar 2025 13:32:34 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3369: fix: EOFException on PreparedStatement#toString with unset bytea parameter since 42.7.4
In-Reply-To: <gh-pgjdbc-pgjdbc-3369@github.com>
References: <gh-pgjdbc-pgjdbc-3369@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: MrEasy
X-GitHub-Comment-Id: 2740473222
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3369
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3369#issuecomment-2740473222
Content-Type: text/plain; charset=utf-8

> > > Could you keep the old method names and signatures?
> > 
> > 
> > @kimjand added a method, that differs from existing one (see javadoc), not sure what you @vlsi mean with keeping the old names?
> 
> Instead of using toStringLiteral() use toString()

From javadoc, I'd assume this was on purpose. @kimjand could you comment on this?

Would be great if we can get the fix into next release, as this blocks our update to recent versions.