Received: from druid.net (root@druid.net [198.96.119.226]) by hub.org (8.9.2/8.9.1) with ESMTP id GAA72411 for ; Thu, 25 Mar 1999 06:58:04 -0500 (EST) (envelope-from darcy@druid.net) Received: from localhost (1712 bytes) by druid.net via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 25 Mar 1999 06:57:48 -0500 (EST) (Smail-3.2.0.104 1998-Nov-20 #2 built 1999-Feb-16) Message-Id: Subject: Re: [INTERFACES] best postgres interface In-Reply-To: from "j. eidsness" at "Mar 25, 1999 01:33:22 am" To: tempest@wolfen.com (j. eidsness) Date: Thu, 25 Mar 1999 06:57:48 -0500 (EST) From: "D'Arcy" "J.M." Cain Cc: eric@broken.net, pgsql-interfaces@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL50 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Thus spake j. eidsness > = 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 cannot tell you what the 'best' interface is, but i can tell you > that *I* use perl (mostly cause i dunno C or C++) and it works fine. It's > very flexible and returns tuples in a very managable manner. So far i have > no reason to knock it, other than the fact that you application is already > writeen in some other language (or you jus hate perl :) I don't like Perl myself. I used to use Tcl which has an interface in the tree as well but since I discovered Python I'm using that almost exclusively. The interface to it is also in the tree or information can be found at http://www.druid.net/pygresql/. -- D'Arcy J.M. Cain | Democracy is three wolves http://www.druid.net/darcy/ | and a sheep voting on +1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.