Re: any reason *not* to use PEAR DB module when accessing mysql?
| From: | Nilesh Govindarajan | Date: | Fri, 19 Mar 2010 16:10:11 +0000 |
| Subject: | Re: any reason *not* to use PEAR DB module when accessing mysql? | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-303014@lists.php.net to get a copy of this message | ||
On 03/19/2010 08:51 PM, Rene Veerman wrote:
another option: adodb.sf.net. and yep, i'm fully for using a db abstraction layer. On Fri, Mar 19, 2010 at 3:17 PM, Robert P. J. Day<rpjday@crashcourse.ca> wrote:Adodb is the same one that is available in Visual Basic. I suggest PDO. Easy to use and portable. -- Nilesh Govindarajan Site & Server Administrator www.itech7.com(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, CANADALinux Consulting, Training and Kernel Pedantry.Web page: http://crashcourse.ca Twitter: http://twitter.com/rpjday======================================================================== -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php