Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113004
MIME-Version: 1.0
References: <CAGBsUrddzJQu3JtqCdLjyHOBf71gj5LpNKuV=OmYGm0Vd3n9Yw@mail.gmail.com>
 <0edafce4-c9a5-c483-65f1-72e49614135a@telia.com> <CAGBsUreBNSkv7KY6FRw-c0SfWDMs9H+aTFG_e89wUSmf53DWkQ@mail.gmail.com>
 <AAA0C162-26F9-4F06-8509-F3C96C0DAEA3@cschneid.com> <CAFPFaMJE-YzYv1nW9t8974CmigrmBtQTQR67BaQ7zbM0B1U4+g@mail.gmail.com>
 <EFFA9BF8-1C86-42E4-9A13-8203B920C81A@cschneid.com> <CAFPFaMKH2rT=9E5ka5YP7DYjZ243QVj-Oj3Bm9kAoA=WBPH2bw@mail.gmail.com>
 <4D7D042F-39A5-4BEF-93B6-542FD53928A1@cschneid.com> <CAAwdEzD84xDnUsOLBTP_BfrT8s97GkOM-aQ7rk7R6x5OFcmVZw@mail.gmail.com>
 <73C12DD2-D99E-44BA-B557-6043F3DDD4C7@cschneid.com> <CAF+90c_QC6wbzQLop3Xyp1RUEeBVSttz6T9KgV4DBJmEL9hmpA@mail.gmail.com>
 <30C0E1A8-6269-4221-AF21-3FA738D5910C@cschneid.com>
In-Reply-To: <30C0E1A8-6269-4221-AF21-3FA738D5910C@cschneid.com>
Date: Wed, 27 Jan 2021 15:48:24 +0100
Message-ID: <CAF+90c9Hv+iZGG7NMJh6P+NXKby07D7K=dS_QGOyMsJg6-HoRA@mail.gmail.com>
To: Christian Schneider <cschneid@cschneid.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000e3c3dc05b9e2dd1d"
Subject: Re: [PHP-DEV] [RFC]: Change Default mysqli Error Mode
From: nikita.ppv@gmail.com (Nikita Popov)

--000000000000e3c3dc05b9e2dd1d
Content-Type: text/plain; charset="UTF-8"

On Wed, Jan 27, 2021 at 3:35 PM Christian Schneider <cschneid@cschneid.com>
wrote:

> Am 27.01.2021 um 14:34 schrieb Nikita Popov <nikita.ppv@gmail.com>:
> > I think if you wanted to introduce an additional diagnostic step, the
> way to go about it would be to issue a deprecation warning when creating a
> connection without mysqli_report() having been explicitly called beforehand.
>
> Wouldn't this mean everybody would add mysqli_report() to their code?
> And wouldn't this render the default of mysqli_report() entirely useless?
> Or is your idea that at a later stage you then want to create a warning
> for manual mysqli_report() calls?
>

Yes, that would render a call to mysqli_report() required until the version
where the default was switched, and the requirement went away. A call to
mysqli_report() is already required if you use exception-based error
handling. The deprecation would force those people who use manual error
handling by default to make an explicit choice.


> > As others have said, the warning mode is pretty much entirely useless,
> and what you really want (presumably) is to know about the places where you
> need to explicitly call mysqli_report() to preserve the old behavior (or
> explicitly switch to the new one).
>
> No, I want to know if I have any code which needs fixing so I can see how
> I want to change those places e.g. a duplicate key from INSERT to REPLACE
> or whatever the correct fix is. Without the code aborting.
>

Okay, I think I now get what you want. My line of thinking was that people
who use manual error handling likely just want to keep doing that, and
should opt-in to it once the default changes. You apparently want them to
switch to use exceptions, in which case the warning mode might indeed be
useful to identify cases where "expected" errors occur.

However, I don't think this has much to do with the proposal at hand. If
someone wants to migrate their code to use exceptions, that's of course
great, but they could do that any time, regardless of what the default is.
They could have done that ten years ago, and they could do it in ten years.

This proposal is only about switching the default, which is why I mentioned
the possibility of diagnosing cases where it may be observable. That said,
I don't think doing so would actually be particularly useful in practice.
And it wouldn't even address your particular concern. As such, I think the
RFC should stick with the original proposal of simply flipping the default
directly.

Regards,
Nikita

--000000000000e3c3dc05b9e2dd1d--