Hi
The use case is pretty simple; my system has thrown an SQL error code, I
want to know what it means.
Having the list in 'order by sqlstate' sequence would save me from having to
hunt up and down the list. And I can easily determine if the error code is
missing; I can then raise another bug report.
Regards
Andy Dossett
-----Original Message-----
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: 27 April 2018 16:16
To: Bruce Momjian <bruce@momjian.us>
Cc: dossett@btinternet.com; pgsql-docs@lists.postgresql.org
Subject: Re: Appendix A. PostgreSQL Error Codes
Bruce Momjian <bruce@momjian.us> writes:
> On Fri, Apr 27, 2018 at 10:08:12AM +0000, PG Doc comments form wrote:
>> Would it be possible to present the codes in ascending sequence?
> Uh, I am guessing this is the order listed in the SQL standard. How
> would you order them differently? Have the letters only at the end?
There was some discussion of this a couple months ago, which I'm too lazy to
search the archives for right now, but it trailed off without any agreement
on what to do.
There are at least three different ordering principles that might be applied
here: numeric by code (well, perhaps more like "ASCII sort order");
alphabetical by exception name (but probably still keeping the
000 category codes at the top); or semantic grouping (ie try to keep related
errors together). It looks to me like all three of these have been applied
in different places ;-).
One idea that might help is to present two tables with different sort
orders, say strict numeric and strict alphabetical. (If we did that, I'd be
inclined to leave errcodes.txt alone and put the sorting responsibility on
the script that converts it to SGML.)
One question that has to be asked is what we think the use-case for this
table is at all. Different use-cases result in different ideas about the
best ordering.
regards, tom lane
