pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: David <dbree@duo-county.com>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Sean Davis <sdavis2@mail.nih.gov>
Cc: David <dbree@duo-county.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: pgperl vs dbd-perl
Date: Wed, 10 Aug 2005 15:22:14 -0500
Message-ID: <20050810202214.GA1935@localhost.localdomain> (raw)
In-Reply-To: <42F9744D.5000408@commandprompt.com>
References: <BF1E3CA5.C038%sdavis2@mail.nih.gov>
	<42F9744D.5000408@commandprompt.com>

On Tue, Aug 09, 2005 at 08:28:13PM -0700, Joshua D. Drake wrote:

> >>Is PgPerl still viable or is DBD the way to go?

> >DBD::Pg is the way to go, for numerous reasons.  DBI is very well 
> >supported.

> DBI/DBD is also what Perl considers standard.
> 
> Sincerely,
> 
> Joshua D. Drake

Well, it's still unanimous, and coming from people who have my respect.

Spent yesterday reading the DBD::Pg mailing list.  Now plan on studying
the manpages for DBD and for DBI.  It shouldn't be much of a chore
rewriting what little I've done so far into DBI code.

Thanks again to everyone who replied.  Maybe I've already said it, but I
thought I was seeing just what all of you have said, but just wasn't
sure.



view thread (5+ messages)

Message-ID: <20050810202214.GA1935@localhost.localdomain>
Permalink:  ../20050810202214.GA1935@localhost.localdomain/
Also on:    postgresql.org/message-id/20050810202214.GA1935@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: dbree@duo-county.com, jd@commandprompt.com, sdavis2@mail.nih.gov
  Subject: Re: pgperl vs dbd-perl
  In-Reply-To: <20050810202214.GA1935@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox