Date: Thu, 13 Mar 2003 21:01:01 -0600
From: Larry Rosenman <ler@lerctr.org>
To: Neil Conway <neilc@samurai.com>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>,
	PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
	Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Upgrading the backend's error-message infrastructure
Message-ID: <59370000.1047610861@lerlaptop.lerctr.org>
In-Reply-To: <1047610701.359.1861.camel@tokyo>
References: <9168.1047588660@sss.pgh.pa.us>	
	<0cfd01c2e9cf$c16ea070$6500a8c0@fhp.internal>	
	<1047609869.357.1856.camel@tokyo>	
	<47640000.1047610098@lerlaptop.lerctr.org>
	<1047610701.359.1861.camel@tokyo>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--On Thursday, March 13, 2003 21:58:21 -0500 Neil Conway 
<neilc@samurai.com> wrote:

> On Thu, 2003-03-13 at 21:48, Larry Rosenman wrote:
>> > Is there any benefit to having this over just including an index of
>> > error codes in the documentation?
>
>> yes, it makes it script-able
>
> What need would you have for it to be script-able? The backend will
> return the error text whenever it returns an error code -- in what
> situation would a client app have the error code but not the error
> message as well?
PHP, returning just the code to a user, and wanting to, later, return the 
full text
in a log-analysis, just as one example.
>
>> and probably more up to date than documentation....
>
> The way to fix that is to keep the documentation up to date, not invent
> pseudo-documentation.
machine readable Error messages and Codes are ALWAYS a good thing, IMNSHO.


>
> Cheers,
>
> Neil
>
> --
> Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
>
>


-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 972-414-9812                 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749