From: | Andreas Zeugswetter <andreas(dot)zeugswetter(at)telecom(dot)at> |
---|---|
To: | "'Vadim Mikheev'" <vadim(at)krs(dot)ru> |
Cc: | "'hackers(at)postgresql(dot)org'" <hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] error messages not only English |
Date: | 1998-05-26 17:47:20 |
Message-ID: | 01BD88DF.3C688810@zeugswettera.user.lan.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Yes, there is a preferred standard, it defines char(5) strings that correspond to specific errors.
It is in SQLSTATE in ESQL/C programs and conforms to X/Open and ANSI.
It consits of numbers and upper case letters only. The first 2 digits are the Class the, last 3
are the subclass. I think only the Class is in the norm.
e.g.: 02000 No data found or End of data reached
00000 Success.
0A000 Feature not supported
You get additional info through:
exec sql get diagnostics :num_rows_affected = ROW_COUNT [, :num = NUMBER, ...];
The integer SQLCODE + the sqlca structure is from an old ANSI norm:
0 Success
100 end of data
< 0 execution not successful
> 0 warning
Andreas
----------
Von: Vadim Mikheev[SMTP:vadim(at)krs(dot)ru]
Gesendet: Dienstag, 26. Mai 1998 18:43
An: Zeugswetter Andreas SARZ
Cc: 'hackers(at)postgresql(dot)org'; 'mimo(at)interdata(dot)com(dot)pl'
Betreff: Re: [HACKERS] error messages not only English
Andreas Zeugswetter wrote:
>
> Anyway, we are still missing the first step in this direction: enumerate ERROR messages.
BTW, are error codes in standard ?
Vadim
From | Date | Subject | |
---|---|---|---|
Next Message | David Gould | 1998-05-26 17:52:40 | Re: [HACKERS] Current sources? |
Previous Message | The Hermit Hacker | 1998-05-26 17:19:27 | Re: [HACKERS] Current sources? |