X-Original-To: pgsql-hackers@postgresql.org Received: from bob.samurai.com (bob.samurai.com [205.207.28.75]) by postgresql.org (Postfix) with ESMTP id DF05C475A71 for ; Thu, 13 Mar 2003 21:58:19 -0500 (EST) Received: from DU150.N224.ResNet.QueensU.CA (DU150.N224.ResNet.QueensU.CA [130.15.224.150]) by bob.samurai.com (Postfix) with ESMTP id CFC981D8C; Thu, 13 Mar 2003 21:58:23 -0500 (EST) Subject: Re: Upgrading the backend's error-message infrastructure From: Neil Conway To: Larry Rosenman Cc: Christopher Kings-Lynne , PostgreSQL Hackers , Tom Lane 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> Content-Type: text/plain Organization: Message-Id: <1047610701.359.1861.camel@tokyo> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 13 Mar 2003 21:58:21 -0500 Content-Transfer-Encoding: 7bit X-Archive-Number: 200303/597 X-Sequence-Number: 36843 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 || PGP Key ID: DB3C29FC