RE: [INTERFACES] best postgres interface

I like perl, but not for database work. I mainly use it for cgi, and for
transforming data into a form that can be imported into a database.

Depending on what I'm working on, I prefer either JDBC or libpq.

--
Peter T Mount, IT Section
petermount(at)it(dot)maidstone(dot)gov(dot)uk
Anything I write here are my own views, and cannot be taken as the
official words of Maidstone Borough Council

-----Original Message-----
From: D'Arcy" "J.M." Cain [mailto:darcy(at)druid(dot)net]
Sent: Thursday, March 25, 1999 11:58 AM
To: tempest(at)wolfen(dot)com
Cc: eric(at)broken(dot)net; pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] best postgres interface

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 <darcy(at){druid|vex}.net> | 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.