Johannes Schlüter wrote:
On Sat, 2011-09-03 at 10:06 +0100, Lester Caine wrote:
> OK done that ...
>
> http://lsces.co.uk/PHP/testphpinfo.php is the current PHP install managed
via
> SUSE. Additional .ini files shows what I've added from the package manager
(and
> my own extension builds), yet mysqlnd is listed as well.
You have a point of which i wasn't aware.
mysqlnd is not yet default from php.net side but SuSE has chosen to do
so. Now there is one consequence: If mysqlnd is used it will be built
statically in PHP, even on Unix, even if the other MySQL modules are
built shared. This can be fixed by adding a specific configuration
option to enforce mysqlnd being build as its own shared .so, too.
Doing this will add a small dependency issue as one has to ensure to
load mysqlnd first, then the other MySQL extensions. I think all
distributions are using a single mysql.ini file to activate all MySQL
extensions they would be able to list mysqlnd first in there and be
done.
This is actually the area that I find very nice in the way all the distributions
handle extensions ... Piling everything into php.ini makes for a large amount of
redundant settings. Adding a separate .ini for each package makes a lot more
sense, and all of the extension specific settings can be kept in the one place.
You can then load a database driver along with all it's own configuration simply
by enabling an .ini file? And optional configurations are handled away from the
core php.ini.
--
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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
