Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55105
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain oracle.com from 148.87.113.117 cause and error)
To: Stas Malyshev <smalyshev@sugarcrm.com>
Cc: Christopher Jones <christopher.jones@oracle.com>, internals@lists.php.net
In-Reply-To: <4E612D70.70606@sugarcrm.com>
References: <1314966424.2150.26.camel@guybrush>
	 <4E60F712.4010901@lerdorf.com> <4E612BBA.2000509@oracle.com>
	 <4E612D70.70606@sugarcrm.com>
Content-Type: text/plain; charset="UTF-8"
Organization: Oracle Corporation
Date: Fri, 02 Sep 2011 22:14:43 +0200
Message-ID: <1314994484.2150.49.camel@guybrush>
Mime-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Make mysqlnd default over libmysql in 5.4
From: johannes.schlueter@oracle.com (Johannes =?ISO-8859-1?Q?Schl=FCter?=)

On Fri, 2011-09-02 at 12:24 -0700, Stas Malyshev wrote:
> Hi!
>=20
> On 9/2/11 12:17 PM, Christopher Jones wrote:
> > I'm +1 for this.  I think the decision&  implementation needs to be don=
e
> > before Beta or deferred to trunk.
>=20
> Frankly, I'd be more comfortable with trunk. We have enough trouble with=
=20
> unit tests etc. before the beta, and introducing profound change in=20
> default without enough time for discussion and gathering feedback from=
=20
> packagers, etc. doesn't look a smart thing to do.

Actually the testing point was the trigger for me to write this mail.
I/We should have done it earlier but for me it's too normal to build
using mysqlnd.

Looking at the tests we have: Most tests are written with mysqlnd in
focus. mysqlnd is what we (Oracle/MySQL) test the most in PHP
perspective for quite some time already. By making mysqlnd the default
we remove one moving piece out of the test equation which simplifies
tests[1]. (we still have multiple server versions to keep in mind ...)
Looking at the last test results Rasmus' sent (using my own would be a
lame cheat ;-) ) he had 6 mysqlnd test failures of which we fixed most
(we also fixed others) whereas libmysql builds have more (depending on
versions). Yes we could spend a few more days and do massive builds of
different combinations (and make the tests more complex to cover
multiple cases) or focus on having a good and stable default which
behaves the same on all platforms.

Looking at distributions: On Windows (which probably is the single most
used build of PHP at all) we're using mysqlnd by default since 5.3.0.
This had some pain in the beginning but went, aside from the recent
OpenSSL issue, quite soomthly. Some other packagers we could meanwhile
convince to use mysqlnd others told me things which boil down to "if PHP
makes it default we use it". So I see little risk there.

johannes

[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

--=20
Johannes Schl=C3=BCter, Oracle
MySQL Engineering - connectors and Client Connectivity