X-Original-To: pgsql-interfaces-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 65A87529B2
	for <pgsql-interfaces-postgresql.org@localhost.postgresql.org>;
	Wed, 10 Aug 2005 00:28:17 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 15487-07
	for <pgsql-interfaces-postgresql.org@localhost.postgresql.org>;
	Wed, 10 Aug 2005 03:28:15 +0000 (GMT)
Received: from hosting.commandprompt.com (128.commandprompt.com
	[207.173.200.128])
	by svr1.postgresql.org (Postfix) with ESMTP id D3BAB5289B
	for <pgsql-interfaces@postgresql.org>;
	Wed, 10 Aug 2005 00:28:14 -0300 (ADT)
Received: from [192.168.1.105] (clbb-248.saw.net [64.146.135.248])
	(authenticated bits=0)
	by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id
	j7A3R60g026168; Tue, 9 Aug 2005 20:27:07 -0700
Message-ID: <42F9744D.5000408@commandprompt.com>
Date: Tue, 09 Aug 2005 20:28:13 -0700
From: "Joshua D. Drake" <jd@commandprompt.com>
Organization: Command Prompt, Inc.
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Sean Davis <sdavis2@mail.nih.gov>
Cc: David <dbree@duo-county.com>, pgsql-interfaces@postgresql.org
Subject: Re: pgperl vs dbd-perl
References: <BF1E3CA5.C038%sdavis2@mail.nih.gov>
In-Reply-To: <BF1E3CA5.C038%sdavis2@mail.nih.gov>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by
	milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]);
	Tue, 09 Aug 2005 20:27:07 -0700 (PDT)
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.024 tagged_above=0 required=5 tests=AWL
X-Spam-Level: 
X-Archive-Number: 200508/10
X-Sequence-Number: 5681

>>
>>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