Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113154 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 86306 invoked from network); 12 Feb 2021 15:32:18 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 12 Feb 2021 15:32:18 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5F6511804CF for ; Fri, 12 Feb 2021 07:18:03 -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=0.8 required=5.0 tests=BAYES_50,SPF_HELO_NONE, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from darkcity.gna.ch (darkcity.gna.ch [195.49.47.11]) (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 ; Fri, 12 Feb 2021 07:18:02 -0800 (PST) Received: from wafer.home (unknown [IPv6:2a02:1205:5053:a220:f8c2:4035:6ab8:9f13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by darkcity.gna.ch (Postfix) with ESMTPSA id 216541517D84; Fri, 12 Feb 2021 16:17:59 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) In-Reply-To: Date: Fri, 12 Feb 2021 16:17:59 +0100 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: <303C832F-CAE7-44F4-B879-33C054825953@cschneid.com> References: <5D0AC588-7BBC-419D-BFEA-06E2E112D3F8@cschneid.com> To: Craig Francis X-Mailer: Apple Mail (2.3654.60.0.2.21) Subject: Re: [PHP-DEV] [VOTE]: Change Default mysqli Error Mode From: cschneid@cschneid.com (Christian Schneider) Am 12.02.2021 um 15:30 schrieb Craig Francis : > Switching the default from `OFF` to `ERROR` to `ERROR | STRICT` isn't = an obvious step, as that still means you're still having a single step = to change from error reporting to exceptions. It is the usual step for (almost) all BC breaking changes in PHP: Warn = first (leaving time to find and adapt code), explode later. The question is not *if* the change has to be made (or how big it is) = but *when* (and how to find places to be changed). Point in case: We just made the transition to PHP 8 and stuff like = round(null) and abs(null) going directly from silence to Exception = resulted in e.g. data importers suddenly stopping to work. Yes, each = individual fix was easy but if there would have been a period where this = is a warning we could have fixed those places without time pressure or a = time window where users saw missing data. - Chris