pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedbest postgres interface
6+ messages / 6 participants
[nested] [flat]
* best postgres interface
@ 1999-03-25 07:10 Eric Enockson <eric@broken.net>
1999-03-25 09:33 ` Re: [INTERFACES] best postgres interface j. eidsness <tempest@wolfen.com>
1999-03-25 14:32 ` Re: [INTERFACES] best postgres interface Gene Selkov Jr. <selkovjr@xnet.com>
1999-03-25 15:10 ` Re: [INTERFACES] best postgres interface Gene Selkov, Jr. <selkovjr@mcs.anl.gov>
0 siblings, 3 replies; 6+ messages in thread
From: Eric Enockson @ 1999-03-25 07:10 UTC (permalink / raw)
To: pgsql-interfaces
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.
Thanks in advance
Eric enockson
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] best postgres interface
1999-03-25 07:10 best postgres interface Eric Enockson <eric@broken.net>
@ 1999-03-25 09:33 ` j. eidsness <tempest@wolfen.com>
1999-03-25 11:57 ` Re: [INTERFACES] best postgres interface D'Arcy J.M. Cain <darcy@druid.net>
2 siblings, 1 reply; 6+ messages in thread
From: j. eidsness @ 1999-03-25 09:33 UTC (permalink / raw)
To: Eric Enockson <eric@broken.net>; +Cc: pgsql-interfaces
On Wed, 24 Mar 1999, Eric Enockson wrote:
=
= 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.
=
= Thanks in advance
= Eric enockson
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 :)
[ ======================= jeff eidsness = ]
[ = webmaster =========================== ]
[ ===== http://www.wolfen.com/calendar/ = ]
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] best postgres interface
1999-03-25 07:10 best postgres interface Eric Enockson <eric@broken.net>
1999-03-25 09:33 ` Re: [INTERFACES] best postgres interface j. eidsness <tempest@wolfen.com>
@ 1999-03-25 11:57 ` D'Arcy J.M. Cain <darcy@druid.net>
0 siblings, 0 replies; 6+ messages in thread
From: "D'Arcy" "J.M." Cain @ 1999-03-25 11:57 UTC (permalink / raw)
To: tempest@wolfen.com; +Cc: eric@broken.net; 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
http://www.druid.net/pygresql/.
--
D'Arcy J.M. Cain <darcy@{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.
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] best postgres interface
1999-03-25 07:10 best postgres interface Eric Enockson <eric@broken.net>
@ 1999-03-25 14:32 ` Gene Selkov Jr. <selkovjr@xnet.com>
2 siblings, 0 replies; 6+ messages in thread
From: Gene Selkov Jr. @ 1999-03-25 14:32 UTC (permalink / raw)
To: eric@broken.net; pgsql-interfaces
> 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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [INTERFACES] best postgres interface
1999-03-25 07:10 best postgres interface Eric Enockson <eric@broken.net>
@ 1999-03-25 15:10 ` Gene Selkov, Jr. <selkovjr@mcs.anl.gov>
2 siblings, 0 replies; 6+ messages in thread
From: Gene Selkov, Jr. @ 1999-03-25 15:10 UTC (permalink / raw)
To: pgsql-interfaces
> 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
^ permalink raw reply [nested|flat] 6+ messages in thread
* RE: [INTERFACES] best postgres interface
@ 1999-03-25 12:18 Peter Mount <petermount@it.maidstone.gov.uk>
0 siblings, 0 replies; 6+ messages in thread
From: Peter Mount @ 1999-03-25 12:18 UTC (permalink / raw)
To: pgsql-interfaces
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@it.maidstone.gov.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@druid.net]
Sent: Thursday, March 25, 1999 11:58 AM
To: tempest@wolfen.com
Cc: eric@broken.net; pgsql-interfaces@postgreSQL.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@{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.
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~1999-03-25 15:10 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-03-25 07:10 best postgres interface Eric Enockson <eric@broken.net>
1999-03-25 09:33 ` j. eidsness <tempest@wolfen.com>
1999-03-25 11:57 ` D'Arcy J.M. Cain <darcy@druid.net>
1999-03-25 14:32 ` Gene Selkov Jr. <selkovjr@xnet.com>
1999-03-25 15:10 ` Gene Selkov, Jr. <selkovjr@mcs.anl.gov>
1999-03-25 12:18 RE: [INTERFACES] best postgres interface Peter Mount <petermount@it.maidstone.gov.uk>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox