Received: from antares.mcs.anl.gov (mcs.anl.gov [140.221.9.6])
	by hub.org (8.9.2/8.9.1) with SMTP id LAA97495
	for <pgsql-interfaces@postgreSQL.org>;
	Thu, 25 Mar 1999 11:07:33 -0500 (EST)
	(envelope-from selkovjr@xnet.com)
Received: from xnet.com (selkovjr@selkovjr.xnet.com [205.243.141.67]) by
	antares.mcs.anl.gov (8.6.10/8.6.10) with ESMTP
	id KAA25347 for <pgsql-interfaces@postgreSQL.org>;
	Thu, 25 Mar 1999 10:07:31 -0600
Message-Id: <199903251607.KAA25347@antares.mcs.anl.gov>
To: pgsql-interfaces@postgreSQL.org
From: "Gene Selkov, Jr." <selkovjr@mcs.anl.gov>
Subject: Re: [INTERFACES] best postgres interface 
In-Reply-To: Your message of "Wed, 24 Mar 1999 23:10:32 PST."
	<36F9E168.4FD73415@broken.net>
Date: Thu, 25 Mar 1999 10:10:52 -0500
Sender: selkovjr@xnet.com


> 	I see there are a couple of perl interfaces to 
> postgres.  Does anyone have any comments as to the 
> best?  I would prefer to use perl but if people 
> think is this the wrong way to go i would like
> to know.  
> 

I can only speak about the Pg interface that I am using. The second
one you mentioned is probably DBI::*; I am not familiar with it but it
looks similar. You might consider DBI if you client needs to access
other data sources as well and if you want it to be more portable. As
far as perl vs. others, I guess all interfaces send the queries and
handle results in much the same way. However, by simply being in
perl, you have and added value of being able to process the results in
a very sophisticated manner. If you choose perl, you won't find
yourself among those who complain about the backend not being able to
compute an avg() of something or not getting the date in the format
they please. Also, some of the tasks that still represent a
considerable load on the backend can be trivially solved in perl.

--Gene