| Lists: | pgsql-docs |
|---|
| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Error message listing? |
| Date: | 2003-08-07 23:04:19 |
| Message-ID: | 200308071604.19919.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
Folks,
Am I missing something here? We're preparing for migration, but I can't find
anywhere a centralized list of the new error messages. Is it in the source
somewhere? If so, can we add it to the documentation?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-07 23:21:14 |
| Message-ID: | 9659.1060298474@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Am I missing something here? We're preparing for migration, but I
> can't find anywhere a centralized list of the new error messages. Is
> it in the source somewhere? If so, can we add it to the
> documentation?
You could make one by running gettext --- see
http://developer.postgresql.org/docs/postgres/nls.html#AEN55720
I do not especially see the point of adding such a list to the
documentation, however.
Or were you looking for src/include/utils/errcodes.h ?
regards, tom lane
| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-07 23:33:55 |
| Message-ID: | 200308071633.55336.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
Tom,
> Or were you looking for src/include/utils/errcodes.h ?
More or less.
The issue is that many projects have internal code to handle PG error messages
by parsing them for certain text. The overhaul of message handling is going
to break that code; users need to know what the new messages and/or codes are
before migrating.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | josh(at)agliodbs(dot)com, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-08 07:29:07 |
| Message-ID: | Pine.LNX.4.56.0308080927300.1385@krusty.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
Tom Lane writes:
> Or were you looking for src/include/utils/errcodes.h ?
I think we should put such a list in the documentation, at least for those
error codes that we have really assigned.
--
Peter Eisentraut peter_e(at)gmx(dot)net
| From: | Francois Suter <francois(at)monpetitcoin(dot)com> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-08 11:43:21 |
| Message-ID: | 8315025C-C995-11D7-8B38-000393427520@monpetitcoin.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
> The issue is that many projects have internal code to handle PG error
> messages
> by parsing them for certain text. The overhaul of message handling
> is going
> to break that code; users need to know what the new messages and/or
> codes are
> before migrating.
I concur, I have such an application and it would be really useful to
have the new error messages and codes.
Cheers
---------------
Francois
Home page: http://www.monpetitcoin.com/
"Would Descartes have programmed in Pascal?" - Umberto Eco
| From: | Francois Suter <dba(at)paragraf(dot)ch> |
|---|---|
| To: | josh(at)agliodbs(dot)com |
| Cc: | pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-08 11:59:19 |
| Message-ID: | BDCBF2F2-C997-11D7-8B38-000393427520@paragraf.ch |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
> The issue is that many projects have internal code to handle PG error
> messages
> by parsing them for certain text. The overhaul of message handling
> is going
> to break that code; users need to know what the new messages and/or
> codes are
> before migrating.
I concur, I have such an application and it would be really useful to
have the new error messages and codes.
Cheers
---------------
Francois
Home page: http://www.monpetitcoin.com/
"Would Descartes have programmed in Pascal?" - Umberto Eco
| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | josh(at)agliodbs(dot)com, pgsql-docs(at)postgresql(dot)org |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-08 13:21:51 |
| Message-ID: | 15453.1060348911@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> Tom Lane writes:
>> Or were you looking for src/include/utils/errcodes.h ?
> I think we should put such a list in the documentation, at least for those
> error codes that we have really assigned.
I have no objection to that. I have doubts about the utility of a
listing of message texts, but the SQLSTATE codes seem reasonable to
document.
Would it be possible to generate the list automatically from errcodes.h,
to simplify future maintenance?
regards, tom lane
| From: | elein <elein(at)varlena(dot)com> |
|---|---|
| To: | pgsql-docs(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | elein <elein(at)varlena(dot)com> |
| Subject: | Re: Error message listing? |
| Date: | 2003-08-08 19:42:13 |
| Message-ID: | 20030808124213.H31611@cookie |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Lists: | pgsql-docs |
The point of including the message texts is
for people supporting various versions who
are looking directly at the message texts
for earlier versions.
This also allows them to upgrade the error
handling to use the new error codes instead
of relying on the message text (which is what
we want).
elein
On Fri, Aug 08, 2003 at 09:21:51AM -0400, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Tom Lane writes:
> >> Or were you looking for src/include/utils/errcodes.h ?
>
> > I think we should put such a list in the documentation, at least for those
> > error codes that we have really assigned.
>
> I have no objection to that. I have doubts about the utility of a
> listing of message texts, but the SQLSTATE codes seem reasonable to
> document.
>
> Would it be possible to generate the list automatically from errcodes.h,
> to simplify future maintenance?
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>