From: Neil Conway <neilc@samurai.com>
To: Larry Rosenman <ler@lerctr.org>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Upgrading the backend's error-message infrastructure
Date: 13 Mar 2003 21:58:21 -0500
Message-ID: <1047610701.359.1861.camel@tokyo> (raw)
In-Reply-To: <47640000.1047610098@lerlaptop.lerctr.org>
References: <9168.1047588660@sss.pgh.pa.us>
<0cfd01c2e9cf$c16ea070$6500a8c0@fhp.internal>
<1047609869.357.1856.camel@tokyo>
<47640000.1047610098@lerlaptop.lerctr.org>
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?
> 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.
Cheers,
Neil
--
Neil Conway <neilc@samurai.com> || PGP Key ID: DB3C29FC
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: neilc@samurai.com, ler@lerctr.org, chriskl@familyhealth.com.au, pgsql-hackers@postgresql.org, tgl@sss.pgh.pa.us
Subject: Re: Upgrading the backend's error-message infrastructure
In-Reply-To: <1047610701.359.1861.camel@tokyo>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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