Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121598
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
In-Reply-To: <CAJmy8YHk7j9qfkZYjw1bU2MSam+uZsVs+ArqqvVjZEpkEn=zGA@mail.gmail.com>
Cc: PHP internals <internals@lists.php.net>
Date: Mon, 6 Nov 2023 21:20:07 +0900
Message-ID: <AA8AE900-36F4-4C62-ADAC-CCCA69CABFA4@sakiot.com>
References: <CAJmy8YHk7j9qfkZYjw1bU2MSam+uZsVs+ArqqvVjZEpkEn=zGA@mail.gmail.com>
To: Hans Henrik Bergan <divinity76@gmail.com>
Subject: Re: [PHP-DEV] Fix the inconsistent behavior of PDO::PARAM_XXX
From: saki@sakiot.com (Saki Takamachi)

Hi Hans,

> I think it'd be a good idea if they used FILTER_VALIDATE_BOOLEAN and FILTE=
R_VALIDATE_INTEGER type logic, with an error if conversion fails..

This can be difficult. Forcing an error is highly likely to destroy the exis=
ting user environment.

> I wonder if PDO::PARAM_BOOL_OR_NULL would be worthwhile=20

That's what I thought at first, but I think it might be a good idea to leave=
 it as a fallback, especially for NULL. In fact, there have been proposals t=
o deprecate PARAM_NULL in the past, but none have made it to the voting phas=
e. I have not looked into it in detail yet, but I suspect that during the di=
scussion stage, they may have come to the conclusion that it should not be a=
bolished.

Regards.

Saki=