Re: the case for machine-readable error fields

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Sam Mason <sam(at)samason(dot)me(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: the case for machine-readable error fields
Date: 2009-08-05 18:29:15
Message-ID: 26742.1249496955@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sam Mason <sam(at)samason(dot)me(dot)uk> writes:
> On Wed, Aug 05, 2009 at 12:41:30PM -0500, Kevin Grittner wrote:
>> From the table, the 23xxx series is for integrity constraint
>> violations, but they appear not to have gotten too specific about
>> breaking that down; thereby leaving it as an implementation choice:

> Yes; but somewhere along the line we've got exactly the same integrity
> constraint violation sqlcodes as DB2 (and Derby, but that's not very
> surprising as they're both IBM). Can't find anybody else trying very
> hard though.

BTW, that's because we deliberately borrowed as much as we could from
DB2. See the notes near the top of errcodes.h. As you say, nobody
else seems to care much, so that was the only precedent we could find.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Petr Jelinek 2009-08-05 18:35:54 Re: GRANT ON ALL IN schema
Previous Message Tom Lane 2009-08-05 18:25:20 Re: the case for machine-readable error fields