Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121594
MIME-Version: 1.0
References: <734FB3C6-EBE6-4F35-8738-436AF7D8B161@sakiot.com>
 <129fb16f-8d38-4951-b84d-f25799158e2b@beccati.com> <CAON3zHC-sB7bS3kVDspUdNhxhO_5jh8so56XQLJjwFU8U8dDqQ@mail.gmail.com>
In-Reply-To: <CAON3zHC-sB7bS3kVDspUdNhxhO_5jh8so56XQLJjwFU8U8dDqQ@mail.gmail.com>
Reply-To: Kentaro Takeda <takeda@youmind.jp>
Date: Mon, 6 Nov 2023 01:43:20 +0900
Message-ID: <CAON3zHBsW-k9+=V2XTD2GRs-hio+Cq70bJAcbxCT_X887yq5VQ@mail.gmail.com>
To: Matteo Beccati <php@beccati.com>
Cc: Saki Takamachi <saki@sakiot.com>, PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] Fix the inconsistent behavior of PDO::PARAM_XXX
From: internals@lists.php.net ("Kentaro Takeda via internals")

Hi, Matteo

> Regarding this past issue with PostgreSQL, it can be solved by
> treating numbers larger than `int4` as `unknown` (as is the case now)
> rather than as `int8` (as in previous attempts).

I'm sorry, this was my mistake.

````
select 1::boolean ; -- returns `t`
select 1 = true ; -- `ERROR: operator does not exist: integer = boolean`
````

The conditions for casting and comparison were different.
`PDO_PARAM_INT` still needs to be passed as `unknown` to PostgreSQL.

Thank you!