Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113217
MIME-Version: 1.0
References: <CAGBsUreDc1CgpBawb6LNXMzpjK_9Y3LQW9n4jYB9AaDjmD9n-g@mail.gmail.com>
In-Reply-To: <CAGBsUreDc1CgpBawb6LNXMzpjK_9Y3LQW9n4jYB9AaDjmD9n-g@mail.gmail.com>
Date: Tue, 23 Feb 2021 10:16:59 +0100
Message-ID: <CAEPJdumquQQ-3vOBJGZ=aoKp5O30_M_W=V02YdDkCmfc-jNn5g@mail.gmail.com>
To: Kamil Tekiela <tekiela246@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000018004b05bbfd62b4"
Subject: Re: [PHP-DEV] [VOTE]: Change Default mysqli Error Mode
From: kontakt@beberlei.de (Benjamin Eberlei)

--00000000000018004b05bbfd62b4
Content-Type: text/plain; charset="UTF-8"

On Thu, Feb 11, 2021 at 12:36 AM Kamil Tekiela <tekiela246@gmail.com> wrote:

> Hi internals,
>
> I have started voting on https://wiki.php.net/rfc/mysqli_default_errmode
> The voting period is 2020-02-11 -- 2020-02-28
>

While the change in itself is something I want to see, I voted no on this
proposal because its a BC break that will break a lot of software out there
and there is no attempt at deprecating the old way and guiding users to the
new behavior.

I wish this would be more gradual by requiring the reporting setting in the
constructor, throwing a deprecation warning when none is provided and then
changing this behavior in 9.0

>
> Kind Regards,
> Kamil
>

--00000000000018004b05bbfd62b4--