| From: | Gunnar R|nning <gunnar(at)candleweb(dot)no> |
|---|---|
| To: | lockhart(at)fourpalms(dot)org |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: More on elog and error codes |
| Date: | 2001-03-20 13:39:55 |
| Message-ID: | x6bsqw1rv8.fsf@thor.candleweb.no |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu> writes:
> > 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?
>
Good point, but I guess most of the errors produced are pgsql
specific. If I remember right Sybase had several different SQL types of error
mapped to one of the standard error codes.
Also the JDBC API provides methods to look at the database dependent error
code and standard error code. I've found both useful when working with
Sybase.
cheers,
Gunnar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-03-20 15:21:54 | Re: AW: Re: elog with automatic file, line, and function |
| Previous Message | Larry Rosenman | 2001-03-20 13:31:30 | Re: Re: elog with automatic file, line, and function |