Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:113222
Message-ID: <70af2150f71a0b32dbc0f74d715d608115ed279c.camel@schlueters.de>
To: Kamil Tekiela <tekiela246@gmail.com>, PHP internals
	 <internals@lists.php.net>
Date: Tue, 23 Feb 2021 16:00:29 +0100
In-Reply-To: <CAGBsUreDc1CgpBawb6LNXMzpjK_9Y3LQW9n4jYB9AaDjmD9n-g@mail.gmail.com>
References: 
	<CAGBsUreDc1CgpBawb6LNXMzpjK_9Y3LQW9n4jYB9AaDjmD9n-g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] [VOTE]: Change Default mysqli Error Mode
From: johannes@schlueters.de (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

Hi,

On Wed, 2021-02-10 at 23:35 +0000, Kamil Tekiela wrote:
> I have started voting on 
> https://wiki.php.net/rfc/mysqli_default_errmode
> The voting period is 2020-02-11 -- 2020-02-28


Sorry, I didn't see this before. I agree that Exceptions are the way to
go and it were good if that had been done decades ago where we argued a
lot whether exceptions should be default.

But now there is tons of valid and good code depending on the default
behavior. Also many tutorials, books, ... don't use the exception
paths, but "classic" error handling. All those will become incorrect!

Doing this change will break such could and that breakage will only be
in an error case, thus many users won't notice this for quite a while.

This requires a smarter migration way. (The spontanous idea might be to
give a deprecation note if users don't set a mode at all and after a
while switch default ... but that isn't unproblematic either)

johannes