From: Joshua D. Drake <jd@commandprompt.com>
To: Sean Davis <sdavis2@mail.nih.gov>
Cc: David <dbree@duo-county.com>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: pgperl vs dbd-perl
Date: Tue, 09 Aug 2005 20:28:13 -0700
Message-ID: <42F9744D.5000408@commandprompt.com> (raw)
In-Reply-To: <BF1E3CA5.C038%sdavis2@mail.nih.gov>
References: <BF1E3CA5.C038%sdavis2@mail.nih.gov>
>>
>>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).
DBI/DBD is also what Perl considers standard.
Sincerely,
Joshua D. Drake
>
> Sean
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
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: jd@commandprompt.com, sdavis2@mail.nih.gov, dbree@duo-county.com
Subject: Re: pgperl vs dbd-perl
In-Reply-To: <42F9744D.5000408@commandprompt.com>
* 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