Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:113305 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 53938 invoked from network); 27 Feb 2021 16:34:31 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 27 Feb 2021 16:34:31 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id E668F1804E1 for ; Sat, 27 Feb 2021 08:23:59 -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.4 required=5.0 tests=BAYES_05,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from mail-ej1-f52.google.com (mail-ej1-f52.google.com [209.85.218.52]) (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 08:23:59 -0800 (PST) Received: by mail-ej1-f52.google.com with SMTP id n20so20120582ejb.5 for ; Sat, 27 Feb 2021 08:23:59 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RJbTUTXTQEgx1ALKpdnOpSz89ONhvl201wlY8ezAKg4=; b=m9osOLqpk4ft/rZTQ/cdG2NlS/wv6yd5xIUXzP3C7l9/CbN/wU5u/r3M0eq7RlG12i PJTOwjR/gbv37e7X/l1T3kyqtanuGJQLJZvN5i5t/zsUKqsYPq832etSAun/2FJfHic3 8sqoVUXrz2wkltnbWQUtzez7sESOZoUKN0CnZdEPaMxs/zSsPDFlI7Acn886urVYR+xE WtknbBCSJGvbdMzC2dj6QuvlTTZ4W412okDaw8FufIfiC48HZ5/W74LvUhTSUOxAcKTd rMoz2mQ+9+Ze6aWuRTmszhtiKB+g9ciM5Z4Qh9a22L3CcdZzMcbYl9FuTe9lTHGR/Y8F 2yPw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=RJbTUTXTQEgx1ALKpdnOpSz89ONhvl201wlY8ezAKg4=; b=OFY07B9dWI+zTleHEkcVkMFMyIVRhq+kMtxNfjfpk4ytLP2DOFx9ZDfgxseKSO0Uiw E/Umq2XFZyQa6Bhz4IYTE5hHbji+FrMz2hW4HtjG5a1qZTNo8BRlOjTTh+kMSX7a1HOk DnpAfcvyRKy0HdASlo60jAzCDe91fHezreIyOyq4/YixnuBQz4sydEBLLGUclth2R7Mh Q9fRjVH5NMox1tu1sx7OCZR5uU2ocCWgtlucREBccCKo94SjgF1361Uj1JjFEpJJeeuW dHo5ee1g0urDmd9JOZrDf/5PsKkX/05BgZ0kg582PzchzcLv85d6hrtAaL7fd3tGAztO eL5w== X-Gm-Message-State: AOAM530dZfgE6mms3tN0HcdzGClw0wxzR2N8ZSm7jKLZISaTycVt0Wst CUn+USa3z1q15OGBCQN+mEpFvR3TE0ooE2z8CcUX2Mxc46Af0g== X-Google-Smtp-Source: ABdhPJxZrSE0bSu5rZz1p9PXNGhSGBQLOb5smNyVgXM2zmEPzHGWPgpjvzz99XlDjIQeykQjdjrLPcdaxgm+XcEkcog= X-Received: by 2002:a17:906:3801:: with SMTP id v1mr8623833ejc.353.1614443038132; Sat, 27 Feb 2021 08:23:58 -0800 (PST) MIME-Version: 1.0 References: <84a86f15-313e-1fb3-eb09-7fd6bbdeb5ce@php.net> <821813eb972cd5dad30a0e10385a115a9a8908a2.camel@schlueters.de> In-Reply-To: <821813eb972cd5dad30a0e10385a115a9a8908a2.camel@schlueters.de> Date: Sat, 27 Feb 2021 16:23:47 +0000 Message-ID: To: =?UTF-8?Q?Johannes_Schl=C3=BCter?= Cc: Sebastian Bergmann , PHP internals Content-Type: multipart/alternative; boundary="000000000000cc4c1e05bc53cf52" Subject: Re: [PHP-DEV] [RFC]: Change Default mysqli Error Mode From: tekiela246@gmail.com (Kamil Tekiela) --000000000000cc4c1e05bc53cf52 Content-Type: text/plain; charset="UTF-8" > > 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 don't see why this would be such an issue. If the code fails for any reason then an error is produced. The error might be surprising, but it is not something that would cause problems. In situations where the code depends on the silenced errors to work properly then the developers would know this and they would test for it during the upgrade. This change fixes more problems than it creates. I believe it is still worthy to put it in 8.1. Every PHP release contains backwards-incompatible changes. In comparison to other BC changes PHP has put in minor releases this one has a very easy fix. You don't have to scour the code looking for places to fix. PHP can't improve if we have to think of people who upgrade without reading the release notes. We also shouldn't be held back by outdated tutorials. In fact, this will help people who still use such tutorials. This isn't a major change that would affect everyone on the planet. This will only affect people who still use mysqli and didn't set the error reporting mode before upgrading. I understand your worries but I don't think this is a good enough reason to not go ahead with this change. Kind regards, Kamil --000000000000cc4c1e05bc53cf52--