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

Re: perl return codes

From: selkovjr(at)mcs(dot)anl(dot)gov
To: jr(at)i-bucks(dot)com
Cc: pgsql-interfaces(at)postgresql(dot)org
Subject: Re: perl return codes
Date: 2001-02-27 01:18:54
Message-ID: 200102270118.TAA22314@selkovjr.xnet.com (view raw or flat)
Thread:
Lists: pgsql-interfaces
> I am writing a few perl scripts accessing postgres.   I have used the
> examples in Bruce Momjian's book, where command results are tested.
> (Variables such as PGRES_CONNECTION_OK and PGRES_TUPLES_OK are used).
> Where can I find documentation on these types of variables, for other
> commands?  (source is okay, I just cannot find it).  

These are not exactly variables -- they are the calls to autoloaded
subroutines exported into your name space, so they appear to be
constants. Their values are defined in Pg.xs, in constant().

If you were asking about their meaning, I believe their names are
self-explanatory, but maybe I've just been around for too long. Look
for comments in libpq-fe.h, and if something is still unclear, be sure
to ask again.

Also, consider using DBI. It has a somewhat cleaner interface and its
error handling model is simpler, too. It's just an opinion, of
course. I once had to convert some of my code from Pg to DBI because
my users were high on portability. Nevermind that I never achieved
portablity (because many of the features I use are unique to
postgres). I but I liked it and still stick to it. I have a feeling
that it allows me to code faster and achieve greater sophistication.

--Gene



In response to

pgsql-interfaces by date

Next:From: Dan LykeDate: 2001-02-27 19:25:16
Subject: Double newline bug with DBD::Pg: Where best to fix?
Previous:From: jrDate: 2001-02-27 00:06:13
Subject: perl return codes

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