Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121592
MIME-Version: 1.0
References: <734FB3C6-EBE6-4F35-8738-436AF7D8B161@sakiot.com> <129fb16f-8d38-4951-b84d-f25799158e2b@beccati.com>
In-Reply-To: <129fb16f-8d38-4951-b84d-f25799158e2b@beccati.com>
Reply-To: Kentaro Takeda <takeda@youmind.jp>
Date: Mon, 6 Nov 2023 00:36:55 +0900
Message-ID: <CAON3zHC-sB7bS3kVDspUdNhxhO_5jh8so56XQLJjwFU8U8dDqQ@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,

> The last time I tried to fix the PDO_PARAM_INT behavior on pdo_pgsql I broke Laravel and surely many other projects.
> https://github.com/php/php-src/pull/6801

Thank you for providing an important example.

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).

This approach aligns with PostgreSQL's capability to cast `integer` to
`boolean` but not `smallint` or `bigint`. This consideration is
crucial for ensuring interoperability.

````
postgres=# select 1::integer::boolean ; -- returns `t`
postgres=# select 1::smallint::boolean ; -- `ERROR: cannot cast type
smallint to boolean`
postgres=# select 1::bigint::boolean ; -- `ERROR: cannot cast type
bigint to boolean`
````

It is certainly not realistic to unify behavior across all databases.
Also, as in the example above, there are certainly places where each
database requires individual support.

I think it would be good if a solution could be found that would allow
for more correct behavior without breaking the behavior of existing
applications.

Your insights and contributions are interesting and invaluable. They
are much appreciated.
Best regards