Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:109616 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 41142 invoked from network); 14 Apr 2020 08:23:19 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 14 Apr 2020 08:23:19 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 8B44B1804C2 for ; Mon, 13 Apr 2020 23:52:53 -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=-0.5 required=5.0 tests=BAYES_05,SPF_HELO_NONE, SPF_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS1836 195.49.0.0/17 X-Spam-Virus: No X-Envelope-From: Received: from darkcity.gna.ch (darkcity.gna.ch [195.49.47.11]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Mon, 13 Apr 2020 23:52:52 -0700 (PDT) Received: from flatter.home (unknown [IPv6:2a02:120b:c3f7:5090:a570:72a1:5512:283f]) (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 003B56C1518; Tue, 14 Apr 2020 08:52:38 +0200 (CEST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\)) In-Reply-To: Date: Tue, 14 Apr 2020 08:52:38 +0200 Cc: AllenJB , php internals Content-Transfer-Encoding: quoted-printable Message-ID: <9ACF699A-56EB-4D57-A6C0-A56375B259F0@cschneid.com> References: <1204349d-97ad-cf0f-93c9-4d18a424717e@allenjb.me.uk> To: Derick Rethans X-Mailer: Apple Mail (2.3608.80.23.2.2) Subject: Re: [PHP-DEV] [RFC][VOTE] Change default PDO error mode From: cschneid@cschneid.com (Christian Schneider) Am 14.04.2020 um 03:10 schrieb Derick Rethans : > On Mon, 13 Apr 2020, Christian Schneider wrote: >=20 >> Am 13.04.2020 um 14:41 schrieb AllenJB : >>> As no concerns were raised during the discussion period, the RFC is = unchanged from that originally posted. >>>=20 >>> Previous discussion threads: >>> * https://externals.io/message/109015 >>=20 >> For the record: I did raise concerns in >> https://externals.io/message/109015#109144 >=20 > You did, but you never followed up on his questions: > https://externals.io/message/109015#109178 I tried to keep the mail traffic down and I didn't think my concern = would be discarded because of this. But to answer the question > Is this not just as disruptive to existing code as changing the = default=20 > error handling to warnings? First of all the RFC talks of changing the default error handling to = *exceptions*, not warnings. So yes, I think it should be changed to warnings first. And for that: No, it is not as disrupting as it will write additional = error messages to a log file vs. stopping the program execution. - Chris