Message-ID: <gh-pgjdbc-pgjdbc-3369-rc2098113857@github.com>
From: "davecramer (@davecramer)" <noreply+davecramer@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 20 May 2025 14:20:58 +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: davecramer
X-GitHub-Comment-Id: 2098113857
X-GitHub-Comment-Type: review_comment
X-GitHub-Commit: 7ad73fc304676b98baa2c421a13cb5e9e3c0be06
X-GitHub-Issue: 3369
X-GitHub-Line: 17
X-GitHub-Path: pgjdbc/src/main/java/org/postgresql/core/v3/DefaultSqlSerializationContext.java
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: review_comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3369#discussion_r2098113857
Content-Type: text/plain; charset=utf-8

(on pgjdbc/src/main/java/org/postgresql/core/v3/DefaultSqlSerializationContext.java:17)

I think it would be useful to document why and where each of these are used.
For instance we use IDEMPOTENT to send the query to the backend
STD is standard conforming strings which is a setting in the backend.