any reason *not* to use PEAR DB module when accessing mysql?

From: Date: Fri, 19 Mar 2010 14:17:22 +0000
Subject: any reason *not* to use PEAR DB module when accessing mysql?
Groups: php.general 
Request: Send a blank email to php-general+get-303005@lists.php.net to get a copy of this message
(just a warning -- as a relative newbie to PHP, i'll probably have the occasional dumb question. just humour me.) i'm looking at some existing PHP code that accesses a mysql 5.0 db, and it's coded using the mysql-specific calls: mysql_connect, mysql_select_db, etc, etc. is there any reason i *wouldn't* want to rewrite that code using the more general PEAR DB module, and use mysqli? certainly, as i read it, using the PEAR DB module would make it easier down the road if i suddenly decide to change the DB backend. anyway, any compelling arguments for or against? rday -- ======================================================================== Robert P. J. Day Waterloo, Ontario, CANADA Linux Consulting, Training and Kernel Pedantry. Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday ========================================================================

« previous php.general (#303005) next »