Message-ID: <gh-pgjdbc-pgjdbc-3888-c3626223469@github.com>
From: "ShenFeng312 (@ShenFeng312)" <noreply+ShenFeng312@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 08 Dec 2025 10:37:17 +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: ShenFeng312
X-GitHub-Comment-Id: 3626223469
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-3626223469
Content-Type: text/plain; charset=utf-8

> The naming of `allowSpecialNumeric` looks obscure as well.

Apologies for my poor English. If you think the property name should be modified, feel free to let me know, and I will change it.


I also think adding this property seems quite problematic. That's why I previously forcefully changed its return value. As of now, we don’t have a better solution. I believe dynamically adjusting the type when encountering special return values isn't a good approach. A deterministic return might be better. Do you have any better suggestions for changes?@vlsi