Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113331
MIME-Version: 1.0
References: <CAGBsUreDc1CgpBawb6LNXMzpjK_9Y3LQW9n4jYB9AaDjmD9n-g@mail.gmail.com>
 <70af2150f71a0b32dbc0f74d715d608115ed279c.camel@schlueters.de> <CAGBsUrd0cXt7YzYUxVktUiC-0kE+om8oVM19j4QHm9fPZdGUww@mail.gmail.com>
In-Reply-To: <CAGBsUrd0cXt7YzYUxVktUiC-0kE+om8oVM19j4QHm9fPZdGUww@mail.gmail.com>
Date: Sun, 28 Feb 2021 17:26:27 +0000
Message-ID: <CAFv4g+Ex1vzsswSg-BgX+koBLP8HMsYgpvZpBE5w25ET=ejU+g@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d29d1205bc68cde3"
Subject: Re: [PHP-DEV] [VOTE]: Change Default mysqli Error Mode
From: craig@craigfrancis.co.uk (Craig Francis)

--000000000000d29d1205bc68cde3
Content-Type: text/plain; charset="UTF-8"

On Sun, 28 Feb 2021 at 17:06, Kamil Tekiela <tekiela246@gmail.com> wrote:

> if someone has a proposal on how to introduce a deprecation phase
>


If the extra step is necessary... I liked Nikita's suggestion to "issue a
deprecation warning when creating a connection without mysqli_report()
having been explicitly called beforehand".

This will hopefully prompt old systems, who want to keep the old behaviour,
to proactively add mysqli_report(MYSQLI_REPORT_OFF).

Keeping in mind that anyone using exceptions today is already using this
function; and when the default has changed, we can drop this check,
so mysqli_report() is no longer required by those using exceptions.

Chris, while I liked your thinking, and appreciate your caution about the
change, I'm not sure `MYSQLI_REPORT_ERROR` would clearly show exceptions
will be the new default.

Craig

--000000000000d29d1205bc68cde3--