Re: Make SQL/JSON error code names match SQL standard

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Make SQL/JSON error code names match SQL standard
Date: 2019-08-22 08:56:19
Message-ID: 4fbb0bae-638a-74f1-271e-72993f3c3709@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2019-08-20 13:48, Alexander Korotkov wrote:
> On Tue, Aug 20, 2019 at 11:49 AM Peter Eisentraut
> <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
>> I propose the attached patch to make the new SQL/JSON error code names
>> match the SQL standard. The existing minor differences don't seem
>> necessary.
>
> Thank you for noticing!
> +1 for pushing this

done

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Kyotaro Horiguchi 2019-08-22 09:13:46 Re: when the IndexScan reset to the next ScanKey for in operator
Previous Message Heikki Linnakangas 2019-08-22 08:48:31 Re: Take skip header out of a loop in COPY FROM