Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:112985 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 54741 invoked from network); 25 Jan 2021 16:00:09 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 25 Jan 2021 16:00:09 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 5F1BB1804CF for ; Mon, 25 Jan 2021 07:41:23 -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.0 required=5.0 tests=BAYES_20,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 ; Mon, 25 Jan 2021 07:41:22 -0800 (PST) Received: from wafer.home (unknown [IPv6:2a02:1205:5053:a220:e1ca:d444:5aef:5dec]) (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 423221517ABD; Mon, 25 Jan 2021 16:41:18 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\)) In-Reply-To: Date: Mon, 25 Jan 2021 16:41:17 +0100 Cc: PHP internals Content-Transfer-Encoding: quoted-printable Message-ID: References: <0edafce4-c9a5-c483-65f1-72e49614135a@telia.com> To: Kamil Tekiela X-Mailer: Apple Mail (2.3654.40.0.2.32) Subject: Re: [PHP-DEV] [RFC]: Change Default mysqli Error Mode From: cschneid@cschneid.com (Christian Schneider) Am 21.01.2021 um 23:46 schrieb Kamil Tekiela : > In fact, I don't really see this as a major breaking change. If any = project > really needs the mysqli errors silenced then they can just set the = error > mode back to OFF. The change is aimed at new users, not existing = projects. > Silenced error reporting was a source of confusion for plenty of = beginners > who were unaware of the setting. As this definitely is a BC (applications stop running) I think we should = go through a phase were it throws a warning instead of aborting, i.e. = changing it to mysqli_report(MYSQLI_REPORT_ERROR); first and change it to throw an exception after a grace period. This would be in line with most other newly introduced exceptions for = the default configuration. Plus this would most certainly help people who host other people's = websites who want to upgrade to PHP 8.x. PS: IMHO The same should be (retroactively) done with round() and = friends! - Chris