Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113302 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 47180 invoked from network); 27 Feb 2021 15:33:54 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 27 Feb 2021 15:33:54 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 310BF1804DC for ; Sat, 27 Feb 2021 07:23:26 -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=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail.toneristzuen.de (mail.toneristzuen.de [84.19.169.162]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Sat, 27 Feb 2021 07:23:25 -0800 (PST) Received: from maniacmansion.fritz.box (ppp-188-174-55-8.dynamic.mnet-online.de [188.174.55.8]) by mail.toneristzuen.de (Postfix) with ESMTPSA id E0DB04269F; Sat, 27 Feb 2021 16:23:22 +0100 (CET) Message-ID: <821813eb972cd5dad30a0e10385a115a9a8908a2.camel@schlueters.de> To: Sebastian Bergmann , internals@lists.php.net Date: Sat, 27 Feb 2021 16:23:19 +0100 In-Reply-To: <84a86f15-313e-1fb3-eb09-7fd6bbdeb5ce@php.net> References: <84a86f15-313e-1fb3-eb09-7fd6bbdeb5ce@php.net> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-0ubuntu0.18.04.2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] [RFC]: Change Default mysqli Error Mode From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=) On Wed, 2021-01-27 at 15:17 +0100, Sebastian Bergmann wrote: > Am 25.01.2021 um 11:03 schrieb Nikita Popov: > > Fully support this proposal. Throwing exceptions is the right > > default, it > > matches what PDO does, and restoring the old behavior is one line > > of code. > > I second that emotion. The issue is, as said, that this only happens in an error situation. Thus if users only test "does my site still work after update?" (what many do ...) won't notice this, till something fails, which would have been caught nice beforehand. I agree that the proposed behavior is better, but we have to mind migration paths. johannes