Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55097
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain oracle.com from 141.146.126.227 cause and error)
Message-ID: <4E612BBA.2000509@oracle.com>
Date: Fri, 02 Sep 2011 12:17:14 -0700
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:6.0) Gecko/20110812 Thunderbird/6.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <1314966424.2150.26.camel@guybrush> <4E60F712.4010901@lerdorf.com>
In-Reply-To: <4E60F712.4010901@lerdorf.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [PHP-DEV] Make mysqlnd default over libmysql in 5.4
From: christopher.jones@oracle.com (Christopher Jones)



On 09/02/2011 08:32 AM, Rasmus Lerdorf wrote:
> On 09/02/2011 05:27 AM, Johannes Schlüter wrote:
>> Hi,
>>
>> when building PHP using
>>    (I) ./configure --with-mysql --with-mysqli --with-pdo-mysql
>> you currently get a build using the system default libmysql, usually
>> in /us or
>> such. Alternatively PHP can be built using
>>   (II) ./configure --with-mysqli=mysqlnd [...]
>> to build the MySQL extensions using the mysqlnd library.
>>
>> I would like to change mysqlnd's config9.m4 file to build PHP using
>> mysqlnd when being called in form (I). Users would still be able to
>> enforce libmysql by passing a path, like /usr.
>>
>> There are two main reasons I see for this:
>>    a) Different libmysql versions have slightly different behavior,
>>       which shows in our tests. We can't have both, a good test coverage
>>       and cover all these differences. By using mysqlnd we have a clear
>>       behavior every PHP developer can rely on.
>>    b) We provide different extensions (pecl/mysqlnd_*) which
>>       improve/extend mysqlnd functionality. By having mysqlnd as default
>>       these are better usable by users.
>>
>> Opinions?
>
> I was actually going to suggest doing this in 5.4 and trunk but didn't
> get around to writing the email yet.
>
> -Rasmus
>

I'm +1 for this.  I think the decision & implementation needs to be done
before Beta or deferred to trunk.

Chris

-- 
Email: christopher.jones@oracle.com
Tel:  +1 650 506 8630
Blog:  http://blogs.oracle.com/opal/