Re: AW: Re: More on elog and error codes
От | Peter Eisentraut |
---|---|
Тема | Re: AW: Re: More on elog and error codes |
Дата | |
Msg-id | Pine.LNX.4.30.0103201750450.1639-100000@peter.localdomain обсуждение исходный текст |
Ответ на | AW: Re: More on elog and error codes (Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>) |
Ответы |
Re: AW: Re: More on elog and error codes
|
Список | 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@gmx.net http://yi.org/peter-e/
В списке pgsql-hackers по дате отправления: