Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113152
MIME-Version: 1.0
References: <CAGBsUreDc1CgpBawb6LNXMzpjK_9Y3LQW9n4jYB9AaDjmD9n-g@mail.gmail.com>
 <5D0AC588-7BBC-419D-BFEA-06E2E112D3F8@cschneid.com>
In-Reply-To: <5D0AC588-7BBC-419D-BFEA-06E2E112D3F8@cschneid.com>
Date: Fri, 12 Feb 2021 08:45:03 +0000
Message-ID: <CAJvSBVPUT7fUC8OEAwzQdrByiTbV0cSnqUKNxkgjrynQ8JeZ8g@mail.gmail.com>
To: Christian Schneider <cschneid@cschneid.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000235ed105bb1fa953"
Subject: Re: [PHP-DEV] [VOTE]: Change Default mysqli Error Mode
From: phpmailinglists@gmail.com (Peter Bowyer)

--000000000000235ed105bb1fa953
Content-Type: text/plain; charset="UTF-8"

On Thu, 11 Feb 2021 at 13:31, Christian Schneider <cschneid@cschneid.com>
wrote:

> For the record: I do not think the wording fo the "Backward Incompatible
> Changes" section is appropriate, especially the *only* in "To bring back
> the old behaviour one needs to add only this line before instantiating
> mysqli class". This IMHO downplays the impact for people hosting legacy
> code.
>
> Also: If there would have been an intermediate PHP version with default
> MYSQLI_REPORT_ERROR I would have voted "Yes", but in the current form I
> have to say "No".
>

I voted "No" for the same reasons.

Peter

--000000000000235ed105bb1fa953--