Re: AW: Re: More on elog and error codes

Coming from an IBM Mainframe background, I'm used to ALL OS/Product
messages having a message number, and a fat messages and codes book.

I hope we can do that eventually.
(maybe a database of the error numbers and codes?)

LER

>>>>>>>>>>>>>>>>>> Original Message <<<<<<<<<<<<<<<<<<

On 3/20/01, 10:53:42 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote regarding
Re: AW: [HACKERS] Re: More on elog and error codes:

> 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/

> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?

> http://www.postgresql.org/users-lounge/docs/faq.html