Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55205
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain hristov.com from 91.196.124.214 cause and error)
Message-ID: <4E64875B.5090701@hristov.com>
Date: Mon, 05 Sep 2011 10:24:59 +0200
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.21) Gecko/20110831 Thunderbird/3.1.13 ThunderBrowse/3.8
MIME-Version: 1.0
To: Stas Malyshev <smalyshev@sugarcrm.com>
CC: Ferenc Kovacs <tyra3l@gmail.com>, =?UTF-8?B?Sm9oYW5uZXMgU2NobMO8dGVy?=
 <johannes.schlueter@oracle.com>, 
 Christopher Jones <christopher.jones@oracle.com>,
 "internals@lists.php.net" <internals@lists.php.net>
References: <1314966424.2150.26.camel@guybrush> <4E60F712.4010901@lerdorf.com>	<4E612BBA.2000509@oracle.com> <4E612D70.70606@sugarcrm.com>	<1314994484.2150.49.camel@guybrush> <4E613ECC.2010007@sugarcrm.com> <CAH-PCH6CxJ31qmsVDDSvF2NAX72hfJ0nTdYCe3+24Fv9L01eig@mail.gmail.com> <4E61401C.1060009@sugarcrm.com>
In-Reply-To: <4E61401C.1060009@sugarcrm.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Make mysqlnd default over libmysql in 5.4
From: php@hristov.com (Andrey Hristov)

  Hi Stas,
On 09/02/2011 10:44 PM, Stas Malyshev wrote:
> Hi!
>
> On 9/2/11 1:41 PM, Ferenc Kovacs wrote:
>> I think you missed the referenced [1]:
>>
>> [1] Yes, we will still allow building with libmysql and we will fix bugs
>> reported there and we will verify it works but focus on mysqlnd, as
>> we're actually handling it already
>
> I did not miss it - I do not see what it means. Either we support both -
> and then for the matter of development and testing nothing changes - or
> something changes, namely "we remove one moving piece out of the test
> equation", the moving piece being libmysql - and "remove" means
> "remove". I just don't see how you can have both of these things at the
> same time.

the problem is that libmysql breaks, maybe more often than mysqlnd does. 
We rarely find bugs in mysqli, there are two codepaths in mysqli. If 
there is a bug in libmysql, what do you want:
- SKIP, because either libmysql or the server is buggy, but many tests 
do skip and does anyone read the skip messages? But your environment is 
buggy, which means that your application will possibly FAIL. Instead of 
finding, that your environment is _broken_ you will skip this 
information. Good luck finding later that you hit a bug, which other 
knew about but you did not get that info, because of SKIP
- FAIL, and one does look at the failures. You might then notice that 
your libmysql and/or server is buggy. You might do something, check for 
existing bug, see if it is fixed and possible update or at least you can 
try to assess what the impact on you it will have.

Best,
Andrey