Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:60279
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.83.42 as permitted sender)
MIME-Version: 1.0
Sender: julienpauli@gmail.com
In-Reply-To: <1335271260.13732.49.camel@guybrush>
References: <CAMUwpuTKa=iG_wk-ZX=cL=nsDYDTB2zfeFdN=cYB3DBskLs6=Q@mail.gmail.com>
 <1335269202.13732.34.camel@guybrush> <CAMUwpuR6rBYz6UkSSvyJY4Um9WZJN9zFATOw-7Y6=o+Vw77Ebw@mail.gmail.com>
 <1335271260.13732.49.camel@guybrush>
Date: Tue, 24 Apr 2012 15:33:59 +0200
Message-ID: <CAMUwpuTOAcC6CySNJOO+sPztyQXrx4yv8BoDxTUDh91C0u+wgA@mail.gmail.com>
To: =?ISO-8859-1?Q?Johannes_Schl=FCter?= <johannes.schlueter@oracle.com>
Cc: PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [PHP-DEV] Expose mysqlnd API through all MySQL extensions
From: jpauli@php.net (jpauli)

2012/4/24 Johannes Schl=FCter <johannes.schlueter@oracle.com>:
> On Tue, 2012-04-24 at 14:27 +0200, jpauli wrote:
>> Aha, I like when an internals guy teach me internals stuff :)
>> So, OK for 5.3 , what about supporting that for >=3D5.4 ?
>
> Maybe. ;-)

I can start working on ideas/patches

>
>> >
>> > The other reason is that one idea for mysqlnd was that it doesn't expo=
se
>> > anything to the userland while ext/mysql is legacy and get's no
>> > additions and PDO would allow user-defined functions,while that's not
>> > really nice.
>>
>> That was my first question : Is it better to provide mysqlnd API
>> through all 3 MySQL extensions, or through a common mysqlnd_***() API
>> ?
>> I understand your thoughts, but I disagree as I think it would be much
>> more clean to expose it via mysqlnd_***() API than through each MySQL
>> ext (and for PDO that would be even more dirty). That would as well
>> add more and more #ifdef MYSQLND inside their source...
>> I was thinking the same way libxml2 API is provided inside ext/libxml
>> instead of through each PHP XML extension API.
>
> Well, as said, we couldn't before 5.4. I gave the "historical" reason
> for the current state.

Got it, got it.

>
>> >> What if I choose to only compile pdo_mysql (against mysqlnd) and not
>> >> mysqli ?? I then would be able to use mysqlnd, but I would have acces=
s
>> >> to its statistics, as its functions are part of ext/mysqli... Strange
>> >> as well as embarrassing isn't it ?
>> >
>> > You simply shouldn't do that ;-)
>>
>> ;-) OK, but that can be done easily. More and more people use
>> pdo_mysql and could be able to not compile other MySQL extensions (I
>> got some machines where only pdo_mysql is compiled in)
>
> All distros I recently checked put all three mysql extensions in the
> same package. People who build PHP themselves should be able to fix this
> easily. So this does not seem to be an issue. (while that's irrelevant
> for the mysqli vs. myslqnd question)

Makes sense.


Julien