Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:121582
Return-Path: <saki@sakiot.com>
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 77889 invoked from network); 4 Nov 2023 12:44:17 -0000
Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5)
  by pb1.pair.com with SMTP; 4 Nov 2023 12:44:17 -0000
Received: from php-smtp4.php.net (localhost [127.0.0.1])
	by php-smtp4.php.net (Postfix) with ESMTP id 676941804BC
	for <internals@lists.php.net>; Sat,  4 Nov 2023 05:44:15 -0700 (PDT)
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>; Sat,  4 Nov 2023 05:44:14 -0700 (PDT)
Received: from smtpclient.apple (128.69.239.49.rev.vmobile.jp [49.239.69.128])
	(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 08222401EB;
	Sat,  4 Nov 2023 21:44:11 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=sakiot.com;
	s=default; t=1699101851;
	bh=4j03IJrwsbJ8tMQwCyFGB9X/s7jsJB02sG1+3Mc6gUg=;
	h=From:Subject:Date:References:Cc:In-Reply-To:To:From;
	b=ELJ6b5dIFobb7gPMTsH4O2x8s0C+/xBxiWUpUGKINXHcRpNTCs7o8s5y4Wwk3s4HX
	 sgBBynygtqjFGAGz3vkjyakHB/Fd0T7/LzpJQ315nOC+Y8r+D3zCQ538MK7n0cdMo2
	 +qmDAjavxAXhI+ay2EmiFvHAu6gLmvB5okO/fw1c=
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Date: Sat, 4 Nov 2023 21:43:55 +0900
Message-ID: <9CC70709-1B01-4C41-91CA-54E3FF38B014@sakiot.com>
References: <CAON3zHAcqGC5hnnLxFfJro0aPEhiLJNyGiP_zvRHsOfb4he3Og@mail.gmail.com>
Cc: Ayesh Karunaratne <ayesh@php.watch>,
 PHP internals <internals@lists.php.net>
In-Reply-To: <CAON3zHAcqGC5hnnLxFfJro0aPEhiLJNyGiP_zvRHsOfb4he3Og@mail.gmail.com>
To: Kentaro Takeda <takeda@youmind.jp>
X-Mailer: iPhone Mail (21A360)
Subject: Re: [PHP-DEV] Fix the inconsistent behavior of PDO::PARAM_XXX
From: saki@sakiot.com (Saki Takamachi)

Hi Kentaro,

The case you presented certainly confuses us very much. Although it is outsi=
de the scope of this discussion, it certainly seems like it would be better t=
o improve it from a safety perspective.

BOOL probably has the most problems; for example, when you pass str, the boo=
lean value will be false only in sqlite. This happens because str is convert=
ed to long and then to bool.

At least for this kind of behavior, I don't think it's necessary to maintain=
 compatibility.

Regards.

Saki=