Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113536
To: Matteo Beccati <php@beccati.com>,
 Benjamin Morel <benjamin.morel@gmail.com>,
 PHP Internals <internals@lists.php.net>
References: <CAG9XoMS5QySfvO5eZv=vTiGefcynkOL3mGwq8K5Knq1OQRqWSQ@mail.gmail.com>
 <163c35c6-90ba-c343-b64d-d17f2e2b7766@beccati.com>
Message-ID: <f96b6e6f-0993-4711-2b72-c657ca1b34ac@gmx.de>
Date: Mon, 15 Mar 2021 14:30:31 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101
 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <163c35c6-90ba-c343-b64d-d17f2e2b7766@beccati.com>
Content-Type: text/plain; charset=utf-8
Content-Language: de-DE
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] PDO::PARAM_INT and pgsql driver
From: cmbecker69@gmx.de ("Christoph M. Becker")

On 15.03.2021 at 14:12, Matteo Beccati wrote:

> On 14/03/2021 21:18, Benjamin Morel wrote:
>> This is because the pgsql driver seems to treat everything as PARAM_STR=
,
>> despite being explicitly requested to bind the value as PARAM_INT; the
>> placeholder is therefore replaced with the string '4326' instead of the
>> integer 4326. >
>> [...]
>>
>> Is there any reason why the pgsql driver doesn't respect PDO::PARAM_STR=
?
>
> Looks like a bug to me. I thought this had been fixed a while back, but
> apparently it wasn't. I'll try to find some time to investigate in the
> next few days.

Looks like the problem is in
<https://github.com/php/php-src/blob/php-7.4.16/ext/pdo_pgsql/pgsql_statem=
ent.c#L377-L391>

=2D-
Christoph M. Becker