Re: pgparam extension to the libpq api - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: pgparam extension to the libpq api
Date
Msg-id b42b73150708171111mbdd47e4m47a1b717e72784b1@mail.gmail.com
Whole thread Raw
In response to pgparam extension to the libpq api  ("Merlin Moncure" <mmoncure@gmail.com>)
List pgsql-hackers
On 8/17/07, Merlin Moncure <mmoncure@gmail.com> wrote:
> Attached are some new functions that extend the libpq api to make

after sending the mail, we noticed some dead code that might be
confusing...in PQparamClear there was some legacy code referring to
'slab' which has no effect...ignore.  Also slab and slabsize members
of PGparam are not supposed to be there.

> * The synchronous execution functions (for example PQparamExec), takes
>a pointer to a result and return error status, which is _not_ how the
>other flavors of Exec operate, but is very convenient however.  If you
>pass in NULL the result is discarded for you.  We are stuck on this
>approach, but we like it.

Also, we are _not_ stuck in the **PGresult concept :-). (typo)

merlin


pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Re: cvsweb busted (was Re: [COMMITTERS] pgsql: Repair problems occurring when multiple RI updates have to be)
Next
From: Tom Lane
Date:
Subject: A small rant about coding style for backend functions