From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Neil Conway" <neilc(at)samurai(dot)com> |
Cc: | "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:51:24 |
Message-ID: | 0d9901c2e9d4$9a3ad280$6500a8c0@fhp.internal |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
> On Thu, 2003-03-13 at 21:16, Christopher Kings-Lynne wrote:
> > Would it be possible to do a command line app?
> >
> > bash$ pg_error 1200D
> > Severity: ERROR
> > Message: Division by zero
> > Detail:
> > Hint: Modify statement to prevent zeros appearing in denominators.
>
> Is there any benefit to having this over just including an index of
> error codes in the documentation?
It's quick and easy, especially when there's thousands of error codes.
Ideally, the pg_error app and the error code documentation should be
automatically generated...
You could have a built-in function: pg_print_error(text) returns text, then
the pg_error command line program could just call that, plus the user could
check up errors from within postgresql as well...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2003-03-14 02:52:46 | Re: Hrm. interval() function? |
Previous Message | Larry Rosenman | 2003-03-14 02:50:40 | Re: Hrm. interval() function? |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2003-03-14 02:58:21 | Re: Upgrading the backend's error-message infrastructure |
Previous Message | Larry Rosenman | 2003-03-14 02:48:18 | Re: Upgrading the backend's error-message infrastructure |