From: David <dbree@duo-county.com>
To: Sean Davis <sdavis2@mail.nih.gov>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: pgperl vs dbd-perl
Date: Tue, 9 Aug 2005 11:10:24 -0500
Message-ID: <20050809161024.GC1756@localhost.localdomain> (raw)
In-Reply-To: <BF1E3CA5.C038%sdavis2@mail.nih.gov>
References: <20050809144539.GB1756@localhost.localdomain>
<BF1E3CA5.C038%sdavis2@mail.nih.gov>
On Tue, Aug 09, 2005 at 10:57:41AM -0400, Sean Davis wrote:
> On 8/9/05 10:45 AM, "David" <dbree@duo-county.com> wrote:
>
> > I'm wondering which of the two is considered the best.
> > However, in researching the mailing lists, etc, it seems that DBD:: is
> > getting the most attention - in fact, I see little mention of PgPerl,
> > and the PgPerl list seems rather quiet.
> > 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.
> More importantly, almost all database-related work is done by building on
> DBI. Interfacing your own code with those of others is then relatively
> straightforward. See, for some examples, DBIx::RecordSet or Class::DBI.
> Finally, if you every need to port to another database product (GASP!), DBI
> is fairly easy to adapt (depending on DB-specific SQL).
Well, so far (and quite quickly) I've received two replies and both are
in agreement that DBD is the way to go. and Dirk Jagdmann flatly stated
that PgPerl is outdated.
This was much as I'd suspected so I think I'll move over.
Thanks to both of you for the insight.
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, sdavis2@mail.nih.gov
Subject: Re: pgperl vs dbd-perl
In-Reply-To: <20050809161024.GC1756@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