Message-ID: <gh-pgjdbc-pgjdbc-3760-c3184203830@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Wed, 13 Aug 2025 14:37:36 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3760: fix: Issue #3757 PreparedStatement.toString fails for hex encoded bytea parameter
In-Reply-To: <gh-pgjdbc-pgjdbc-3760@github.com>
References: <gh-pgjdbc-pgjdbc-3760@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 3184203830
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3760
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3760#issuecomment-3184203830
Content-Type: text/plain; charset=utf-8

> I don't think the whitespace handling is necessary, folks could always construct their strings to not have whitespace

There might be an application (or library) that generates literals with whitespaces. As PostgreSQL accepts literals with whitespaces, we should be doing so.