| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
| Cc: | "'lockhart(at)fourpalms(dot)org'" <lockhart(at)fourpalms(dot)org>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: Re: More on elog and error codes |
| Date: | 2001-03-20 16:53:42 |
| Message-ID: | Pine.LNX.4.30.0103201750450.1639-100000@peter.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Zeugswetter Andreas SB writes:
> > SQL9x specifies some error codes, with no particular numbering scheme
> > other than negative numbers indicate a problem afaicr.
> >
> > Shouldn't we map to those where possible?
>
> Yes, it defines at least a few dozen char(5) error codes. These are hierarchical,
> grouped into Warnings and Errors, and have room for implementation specific
> message codes.
Let's use those then to start with.
Anyone got a good idea for a client API to this? I think we could just
prefix the actual message with the error code, at least as a start.
Since they're all fixed width the client could take them apart easily. I
recall other RDBMS' (Oracle?) also having an error code before each
message.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zeugswetter Andreas SB | 2001-03-20 16:53:47 | AW: More on elog and error codes |
| Previous Message | Bruce Momjian | 2001-03-20 16:38:15 | Re: Re: src/test/regress/README duplicates SGML material |