From: | Jürgen Purtz <juergen(at)purtz(dot)de> |
---|---|
To: | pgsql-sql(at)lists(dot)postgresql(dot)org |
Subject: | Re: SQL conformity regarding SQLSTATE |
Date: | 2017-12-21 10:44:46 |
Message-ID: | 6f4d8b10-0d24-86f5-3e14-b3d362181381@purtz.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> I poked around in SQL:2011 and I concur that the first four of those
> no longer appear in the standard. However, unless grep is failing me,
> we aren't generating those errcodes anywhere either:
>
> ERRCODE_WARNING_IMPLICIT_ZERO_BIT_PADDING
> ERRCODE_SQL_STATEMENT_NOT_YET_COMPLETE
> ERRCODE_INVALID_TRANSACTION_INITIATION
> ERRCODE_E_R_I_E_INVALID_SQLSTATE_RETURNED
>
> So we could just remove those codes and be no worse off.
+1.
I rearranged 'errcodes.txt' according to SQLSTATE without eliminating
any row. Please read section 42 and its comments carefully. Maybe you
want to rearrange the 4 rows which have no fourth column. The attachment
contains the changes as raw file and as patch.
Generating the documentation works as expected. I haven't done any other
test.
Kind regards
Jürgen Purtz
Attachment | Content-Type | Size |
---|---|---|
errcodes.txt | text/plain | 30.6 KB |
errcodes.txt.patch | text/x-patch | 26.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-12-21 16:50:32 | Re: SQL conformity regarding SQLSTATE |
Previous Message | Tom Lane | 2017-12-21 01:28:15 | Re: SQL conformity regarding SQLSTATE |