Message-ID: <gh-pgjdbc-pgjdbc-3888-c3626431922@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 08 Dec 2025 11:26:50 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #3888: fix: Issue #3784 pgjdbc can't decode numeric arrays containing special numbers like NaN
In-Reply-To: <gh-pgjdbc-pgjdbc-3888@github.com>
References: <gh-pgjdbc-pgjdbc-3888@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 3626431922
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 3888
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/3888#issuecomment-3626431922
Content-Type: text/plain; charset=utf-8

> I believe dynamically adjusting the type when encountering special return values isn't a good approach.

Yeah, we should not return different types from the same API. The clients would likely end up with `ClassCastException`.