Re: [PATCHES] libpq type system 0.9a - Mailing list pgsql-hackers

From Gregory Stark
Subject Re: [PATCHES] libpq type system 0.9a
Date
Msg-id 87zls1u5am.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: [PATCHES] libpq type system 0.9a  (Andrew Chernow <ac@esilo.com>)
Responses Re: [PATCHES] libpq type system 0.9a  ("Merlin Moncure" <mmoncure@gmail.com>)
List pgsql-hackers
"Andrew Chernow" <ac@esilo.com> writes:

> How would the caller of getvalues know whether the error was generated by a
> libpqtypes API call or by a libpq API call (like PQgetvalue)? PQgetf should
> behave exactely as PQgetvalue does, in regards to errors.

Hm. Well I was thinking of errors from database operations rather than things
like PQgetvalue. 

I suppose we have to decide whether pqtypes is a "wrapper" around libpq in
which case your functions would have to take the libpq error and copy it into
your error state or an additional set of functions which are really part of
appendage of libpq




--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's 24x7 Postgres support!


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [DOCS] [SQL] pl/PgSQL, variable names in NEW
Next
From: Tom Lane
Date:
Subject: Re: [DOCS] [SQL] pl/PgSQL, variable names in NEW