On Fri, Jan 11, 2002 at 10:20:16AM -0700, Mike Schienle wrote:
: Hi all -
: 
: I've been using DBI/DBD with Oracle, Informix and MySQL over the last
: couple of years. I'm considering changing my MySQL DB's to PostgreSQL
: DB's on my web server. O'Reilly just announced a new PostgreSQL book at
: <http://www.oreilly.com/catalog/ppostgresql/>. I know there is a DBD
: module for PostgreSQL, but the table of contents of the book don't
: mention it. Should I read anything into that? Does the PostgreSQL DBD
: lack anything compared to the Oracle or MySQL DBD's, or is it just likely 
: that the author didn't place an emphasis on that aspect?

I have experiences with both the Pg and mysql DBDs.  The mysql one
is certainly more actively developed.  The Pg one works for 95% of
the stuff that we do.  We've run into one or two serious bugs
(crashers), but one can code around them.

: At the risk of starting a religious war, I'd like to know if there is any 
: real downside to switching from MySQL to PostgreSQL, and using DBI/DBD
: for accessing it.

The only downside you're going to find are the down/upsides of
switching from MySQL to PostgreSQL.  The DBI interface won't change
for you.  My personal experience between the two databases is that
MySQL is easier to manage, easier to work with, and enjoys more
active support from the Perl development community.  With MySQL's
InnoDB tables, there's really not much that PostgreSQL has over
MySQL except for very advanced, mostly proprietary extensions (with
the exception of triggers, which are coming).  In everything I've
coded, MySQL beats PostgreSQL hands-down for speed when both are
configured properly.

* Philip Molter
* Texas.net Internet
* http://www.texas.net/
* [EMAIL PROTECTED]

Reply via email to