v8.1: Error severity on libpq PGconn* - Mailing list pgsql-interfaces

From Jeffrey Brendecke
Subject v8.1: Error severity on libpq PGconn*
Date
Msg-id 315963.85252.qm@web26909.mail.ukl.yahoo.com
Whole thread Raw
Responses Re: v8.1: Error severity on libpq PGconn*  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-interfaces
Is there a recommended way to get the error severity (ERROR vs. FATAL vs. PANIC, etc.) off a PGconn* as there is for a
PGresult*using PQresultErrorField()? 

For example, when I pass in a non-existent database name when creating a connection, I get the following message:

FATAL:  database "xxxxxx" does not exist

as returned by PQerrorMessage().

This message format does not fit into my messaging framework and the status returned from PQstatus() is unfortunately
toovague to be of use in this regard. 


I would like to avoid parsing the message, chopping off the text up to the double space, and do some sort of lookup on
thepreceeding localized text to determine the severity. 

The 8.1 docs say there is no PQerrorField() function and the 8.2 and 8.3 docs make the same disclaimer.

I saw some mails back from 2003 in the archives that seem to propose such a solution as PQerrorField(), but it appears
tohave never been implemented. 

Thanks very much.



      __________________________________  Ihre erste Baustelle? Wissenswertes für Bastler und Hobby Handwerker.
www.yahoo.de/clever


pgsql-interfaces by date:

Previous
From: Tom Lane
Date:
Subject: Re: Retrieving multiple error messages via libpq
Next
From: Tom Lane
Date:
Subject: Re: v8.1: Error severity on libpq PGconn*