Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:55117
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.187 cause and error)
Message-ID: <4E614B96.9060500@lsces.co.uk>
Date: Fri, 02 Sep 2011 22:33:10 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:6.0) Gecko/20110815 Firefox/6.0 SeaMonkey/2.3
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <1314966424.2150.26.camel@guybrush> <4E60F712.4010901@lerdorf.com> <4E6139CA.6040805@lsces.co.uk> <4E61411A.40000@phpdoc.de>
In-Reply-To: <4E61411A.40000@phpdoc.de>
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: lester@lsces.co.uk (Lester Caine)

Ulf Wendel wrote:
> Am 02.09.2011 22:17, schrieb Lester Caine:
>> Rasmus Lerdorf wrote:
>>> I was actually going to suggest doing this in 5.4 and trunk but didn't
>>> get around to writing the email yet.
>>
>> It would still be nice to be able to simply switch off MySQL for those
>> of us who do not have it installed ...
>> It gets annoying when PHP forces the installation of MySQL in a
>> distribution and then prevents disabling it. It is another example of
>> why a more modular approach does make sense!
>
> Lester,
>
> do I understand that you are afraid of a PHP which comes with MySQL support that
> cannot be disabled?
>
> I don't think the proposal goes like that. The proposal is to change the default
> library, if not set during compile, used by the MySQL extensions, if enabled,
> from libmysql to mysqlnd. This is independent of the questions:
>
>   - if any MySQL extension shall be enabled by default
>   - if PHP can be built without MySQL support
>
> And, I said it in the other email, this is no attempt to remove libmysql support.
>
> I may be wrong but your concern - as valid as it is - seems a bit off topic, no?

If the MySQL support was loaded as an extension rather than being forced on 
everybody, then you could provide either version of library just by selecting 
the right extension? Just as we provide special builds of other extensions to 
allow backwards compatibility ... we HAD dropped MySQL dependence at one point, 
but it seems to have crept back in without any particular agreement?

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php