Re: svn: /php/php-src/ branches/PHP_5_3/ext/mysqli/tests/connect.inc branches/PHP_5_3/ext/pdo_mysql/tests/mysql_pdo_test.inc
branches/PHP_5_4/ext/mysqli/tests/connect.inc branches/PHP_5_4/ext/pdo_mysql/tests/mysql_pdo_test.inc trunk/ext/mys

From: Date: Fri, 02 Sep 2011 11:36:56 +0000
Subject: Re: svn: /php/php-src/ branches/PHP_5_3/ext/mysqli/tests/connect.inc branches/PHP_5_3/ext/pdo_mysql/tests/mysql_pdo_test.inc
branches/PHP_5_4/ext/mysqli/tests/connect.inc branches/PHP_5_4/ext/pdo_mysql/tests/mysql_pdo_test.inc trunk/ext/mys
References: 1  Groups: php.cvs 
Request: Send a blank email to [email protected] to get a copy of this message 
Am 02.09.2011 13:27, schrieb Hannes Magnusson:

On Fri, Sep 2, 2011 at 13:06, Ulf Wendel<[email protected]>  wrote:

uw                                       Fri, 02 Sep 2011 11:06:51 +0000


Revision: http://svn.php.net/viewvc?view=revision&revision=316034

Log:
Hopefully, this is an even better way to check for InnoDB support as of MySQL 5.6.1



How about creating a native function that can return the list of
supported engines?
Or is that something the client libs don't support without a literal
query, making this way "just as good as any"?


Then you end up with stuff like mysql_list_dbs() or mysql_list_tables() (http://dev.mysql.com/doc/refman/5.5/en/mysql-list-dbs.html) which does not do anything that can't be done easily in user space. I'm not a big fan of such calls in the C API. They bloat up the API.

Is it worth it, if such BC breaks happen only every couple of years or would PHP as such be much better off if, for example, PDO hat proper metadata support, including user space calls specific to a particular DB?

Ulf

Thread (3 messages)

« previous php.cvs (#66154) next »