Re: the case for machine-readable error fields - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: the case for machine-readable error fields
Date
Msg-id 4A7AC9AE020000250002955F@gw.wicourts.gov
Whole thread Raw
In response to Re: the case for machine-readable error fields  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: the case for machine-readable error fields  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
Tom Lane <tgl@sss.pgh.pa.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Adding error message "source"
Next
From: "Todd A. Cook"
Date:
Subject: Re: slow commits with heavy temp table usage in 8.4.0