Re: the case for machine-readable error fields

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Alvaro Herrera" <alvherre(at)commandprompt(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>,"Sam Mason" <sam(at)samason(dot)me(dot)uk>
Subject: Re: the case for machine-readable error fields
Date: 2009-08-06 17:16:46
Message-ID: 4A7AC9AE020000250002955F@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I'm not proposing that we implement GET DIAGNOSTICS as a statement.
> I was just thinking that the list of values it's supposed to make
> available might do as a guide to what extra error fields we need to
> provide where.

>From what I could find on a quick scan:

RETURNED_SQLSTATE
CLASS_ORIGIN
SUBCLASS_ORIGIN
CONSTRAINT_CATALOG
CONSTRAINT_SCHEMA
CONSTRAINT_NAME
CATALOG_NAME
SCHEMA_NAME
TABLE_NAME
COLUMN_NAME
CURSOR_NAME
MESSAGE_TEXT
MESSAGE_LENGTH
MESSAGE_OCTET_LENGTH

CATALOG is, of course, equivalent to database in the PostgreSQL world.

-Kevin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Todd A. Cook 2009-08-06 17:32:44 Re: slow commits with heavy temp table usage in 8.4.0
Previous Message Peter Eisentraut 2009-08-06 17:04:04 Re: Adding error message "source"