Return-Path: pg_adm@postgres.berkeley.edu
Received: by postgres.Berkeley.EDU (5.61/1.29)
	id AA03392; Wed, 2 Jun 93 17:07:04 -0700
Date: Wed, 2 Jun 93 17:07:04 -0700
Message-Id: <9306030007.AA03392@postgres.Berkeley.EDU>
From: jaws@pangaea.dme.nt.gov.au (James Woods 61-89-895256)
Subject: Re: PQexec error handling
To: postgres@postgres.berkeley.edu
Sender: pg_adm@postgres.berkeley.edu

> PQexec currently returns "R" when you get a non-fatal error
> (sometimes setting PQerrormsg, sometimes not) and calls exit(2)
> on most "fatal" (backend coredump) errors.  this interface is
> less than useful for intelligent error-handling.

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.

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

thanks
James Woods
jaws@pangaea.dme.nt.gov.au