On Fri, 19 Mar 2010, Mattias Thorslund wrote:
> Robert P. J. Day wrote:
> > (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
> > --
> >
>
> Well, the reason you shouldn't use PEAR DB in a new project is that
> it's being deprecated. MDB2 is the PEAR successor, ...
you're right and, in fact, i knew that, i just forgot. i'm also
taking seriously the recommendations for PDO and adodb.
rday
--
========================================================================
Robert P. J. Day Waterloo, Ontario, CANADA
Linux 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
