Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA04913; Wed, 2 Jun 93 22:00:54 -0700
Date: Wed, 2 Jun 93 22:00:54 -0700
From: "David J. Hughes" <bambi@Bond.edu.au>
Subject: Re: PQexec error handling
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu
To: James Woods 61-89-895256 <jaws@pangaea.dme.nt.gov.au>
Cc: postgres@postgres.Berkeley.EDU
In-Reply-To: <9306030007.AA03392@postgres.Berkeley.EDU>
Message-Id: <Pine.3.05.9306031438.I16056-b100000@fiddich.its.Bond.edu.au>
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII



On Wed, 2 Jun 1993, James Woods 61-89-895256 wrote:

> This sounds like a great idea.  How about (though this may take a while to 
> implement) after the "R" or "E" supplying an integer representing some sort of 
> error number which ties into a data structure of some sort which supplies more 
> information.  Something which acts similar to the standard errno system.  I
> would guess the tedious part about this would be numbering and rationalising all 
> the error messages.

Hmmm, I thought that was what PQerrormsg was for (ie. a textual
representation of the error).  If the setting of PQerrormsg was a little
more uniform, we'd have a much more workable solution.


> Well just a suggestion, and any improvement will be welcome.

Ditto.


bambi
   ___                                  David J. Hughes    bambi@Bond.edu.au
  /   \                /  /    /        
 /  __/ __   __   ____/  /    / __            Senior Network Programmer
/    \ /  \ /  \ /   /  /    / /  \  /      Comms Development & Operation
\____/ \__//   / \__/   \___/ /   / /   Qld. 4229  AUSTRALIA  (+61 75 951450)



