Message-ID: <gh-pgjdbc-pgjdbc-3888-c3625230783@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Mon, 08 Dec 2025 06:29:44 +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: 3625230783
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-3625230783
Content-Type: text/plain; charset=utf-8

Frankly speaking, adding more options seems fragile.
The naming of `allowSpecialNumeric` looks obscure as well.

In theory, we could have option like `decodeNumericas=bigdecimal|number|...`, however, a global option is hard to use as different use-sites might need different values.

---

The only reason I could find for having a property is to allow temporarily revert to an old behavior.

In other words:
* make sure the default is the old behavoir
* announce the switch in the release notes
* sometime later make the switch
* remove the switch after several years