| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Larry Rosenman <ler(at)lerctr(dot)org> |
| Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: Upgrading the backend's error-message infrastructure |
| Date: | 2003-03-14 02:58:21 |
| Message-ID: | 1047610701.359.1861.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-interfaces |
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(at)samurai(dot)com> || PGP Key ID: DB3C29FC
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-03-14 03:01:01 | Re: Upgrading the backend's error-message infrastructure |
| Previous Message | Christopher Kings-Lynne | 2003-03-14 02:52:46 | Re: Hrm. interval() function? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2003-03-14 03:01:01 | Re: Upgrading the backend's error-message infrastructure |
| Previous Message | Christopher Kings-Lynne | 2003-03-14 02:51:24 | Re: Upgrading the backend's error-message infrastructure |