Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121590
Return-Path: <saki@sakiot.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 52651 invoked from network); 5 Nov 2023 13:52:18 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 5 Nov 2023 13:52:18 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id BCE4A180087
	for <internals@lists.php.net>; Sun,  5 Nov 2023 05:52:16 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_NONE,SPF_PASS,
	T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.2
X-Spam-ASN: AS9370 160.16.128.0/17
X-Spam-Virus: No
X-Envelope-From: <saki@sakiot.com>
Received: from mail.sakiot.com (mail.sakiot.com [160.16.227.216])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256)
	(No client certificate requested)
	by php-smtp4.php.net (Postfix) with ESMTPS
	for <internals@lists.php.net>; Sun,  5 Nov 2023 05:52:15 -0800 (PST)
Received: from smtpclient.apple (31.148.159.133.rev.vmobile.jp [133.159.148.31])
	(using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits))
	(No client certificate requested)
	by mail.sakiot.com (Postfix) with ESMTPSA id E6C4C401E4;
	Sun,  5 Nov 2023 22:52:12 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com;
	s=default; t=1699192332;
	bh=WpTp5OunI67mOQoP9sMAA8yWR4gQQszSOFZuM6GlI1Y=;
	h=Subject:From:In-Reply-To:Cc:Date:References:To:From;
	b=nl2X/kJaAO4fwAFVko3UM6V+2b36ldtFuuGqPilBe3ENCdgmaB5/YJVM9i10F1pPw
	 yqWq8FP1C6Ta4NKdymMQW0LtUWUI+5y2eeO/ldqZAQkPp41iuRXr6gMFttFsK1JfnZ
	 DfKQ6I2URaAoL2z3z6gP1oXGrLXp6sTM2BTdfHiE=
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
In-Reply-To: <129fb16f-8d38-4951-b84d-f25799158e2b@beccati.com>
Cc: PHP internals <internals@lists.php.net>
Date: Sun, 5 Nov 2023 22:52:00 +0900
Message-ID: <EB99B8F2-68F9-4D59-85AC-1691438A34D4@sakiot.com>
References: <129fb16f-8d38-4951-b84d-f25799158e2b@beccati.com>
To: Matteo Beccati <php@beccati.com>
X-Mailer: iPhone Mail (21A360)
Subject: Re: [PHP-DEV] Fix the inconsistent behavior of PDO::PARAM_XXX
From: saki@sakiot.com (Saki Takamachi)

Hi Matteo,

> I'm sure there are several bugs w/ types in PDO.
>=20
> Perhaps some can be fixed, but I would be very careful touching that part.=

>=20
> The last time I tried to fix the PDO_PARAM_INT behaviour on pdo_pgsql I br=
oke Laravel and surely many other projects.
>=20
> I'm afraid that most libraries and projects have now worked around some of=
 the bugs and trying to fix them is going to cause BC problems, or generate a=
 whole new series of bugs and incompatibilities.

I hate to be the person to tell you this, it is simply a problem caused by r=
eleasing broken code.=20

However admittedly, we may need a some more test patterns to compensate for n=
ot breaking functionality.

Regards.

Saki=