Skip site navigation (1) Skip section navigation (2)

Re: [INTERFACES] best postgres interface

From: "D'Arcy" "J(dot)M(dot)" Cain <darcy(at)druid(dot)net>
To: tempest(at)wolfen(dot)com (j(dot) eidsness)
Cc: eric(at)broken(dot)net, pgsql-interfaces(at)postgreSQL(dot)org
Subject: Re: [INTERFACES] best postgres interface
Date: 1999-03-25 11:57:48
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-interfaces
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

D'Arcy J.M. Cain <darcy(at){druid|vex}.net>   |  Democracy is three wolves                |  and a sheep voting on
+1 416 424 2871     (DoD#0082)    (eNTP)   |  what's for dinner.

In response to

pgsql-interfaces by date

Next:From: Brett W. McCoyDate: 1999-03-25 12:18:03
Subject: Re: [INTERFACES] PgAdmin
Previous:From: j. eidsnessDate: 1999-03-25 09:33:22
Subject: Re: [INTERFACES] best postgres interface

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group