Re: Upgrading the backend's error-message infrastructure
Larry Rosenman <ler@lerctr.org>
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>
Date: 2003-03-14T03:01:01Z
Lists: pgsql-hackers
--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