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 >=5.4 ?
Maybe. ;-) > > > > The other reason is that one idea for mysqlnd was that it doesn't expose > > 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. > >> 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 access > >> 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) johannes -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
