| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'lockhart(at)fourpalms(dot)org'" <lockhart(at)fourpalms(dot)org>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | AW: Re: More on elog and error codes |
| Date: | 2001-03-20 16:28:51 |
| Message-ID: | 11C1E6749A55D411A9670001FA687963368255@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > So we need some good error numbering scheme. Any ideas?
>
> 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.
Imho there is no room for inventing something new here, or only in addition.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-20 16:30:20 | Re: Re: src/test/regress/README duplicates SGML material |
| Previous Message | Peter Eisentraut | 2001-03-20 16:25:56 | Re: src/test/regress/README duplicates SGML material |