Message-ID: <gh-pgjdbc-pgjdbc-3062-c4487089839@github.com>
From: "lukaseder (@lukaseder)" <noreply+lukaseder@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Tue, 19 May 2026 11:02:09 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3062: feat: type cache rework, codec API, and composite-type round-trip
In-Reply-To: <gh-pgjdbc-pgjdbc-3062@github.com>
References: <gh-pgjdbc-pgjdbc-3062@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: lukaseder
X-GitHub-Comment-Id: 4487089839
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3062
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3062#issuecomment-4487089839
Content-Type: text/plain; charset=utf-8

What I meant was to ask whether `SQLData` transparently decodes *both* binary and text encodings, or if clients have to be aware of the `binaryTransferEnable` flag as well as `SUPPORTED_BINARY_OIDS` for specific types, when using `SQLData`.