Re: [HACKERS] Upgrading the backend's error-message infrastructure - Mailing list pgsql-interfaces

From Dave Page
Subject Re: [HACKERS] Upgrading the backend's error-message infrastructure
Date
Msg-id 03AF4E498C591348A42FC93DEA9661B8259DDA@mail.vale-housing.co.uk
Whole thread Raw
List pgsql-interfaces

> -----Original Message-----
> From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
> Sent: 18 March 2003 14:45
> To: Peter Eisentraut
> Cc: pgsql-hackers@postgresql.org; pgsql-interfaces@postgresql.org
> Subject: Re: [HACKERS] [INTERFACES] Upgrading the backend's 
> error-message infrastructure 
> 
> 
> I think this is a matter to be solved at the level of the API 
> of each client library.  For example, libpq's PQerrorMessage 
> would presumably construct some unified string out of these 
> three fields and the error severity; plus we'd add new calls 
> to extract the individual fields. I do not think it's 
> appropriate to try to control this from the server side of things.

I agree. It's trivial for ODBC/JDBC etc to concatenate a few strings,
and the flexibility gained by interfaces such as libpq that don't have a
spec to follow would be very welcome (here at least!).

Regards, Dave.

pgsql-interfaces by date:

Previous
From: Sheshu
Date:
Subject: esql problem
Next
From: Bruce Momjian
Date:
Subject: Re: plpython problem.