From: Merlin Moncure <mmoncure@gmail.com>
To: Pavel Golub <pavel@gf.microolap.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: pgsql-interfaces@postgresql.org
Subject: Re: PQdeleteTuple function in libpq
Date: Thu, 2 Jun 2011 08:30:49 -0500
Message-ID: <BANLkTikCxdeBsEBbWOLQXSkLXnuMRVqPug@mail.gmail.com> (raw)
In-Reply-To: <16110385996.20110602112418@gf.microolap.com>
References: <147534417.20110601184310@gf.microolap.com>
<BANLkTim8BxvLLnLL15WjgpVpNX_O0qVAxw@mail.gmail.com>
<16110385996.20110602112418@gf.microolap.com>
On Thu, Jun 2, 2011 at 3:24 AM, Pavel Golub <pavel@microolap.com> wrote:
> MM> well, you have PQaddTuple, but this was exposed mainly for the purpose
> MM> of building a PQresult from outside the libpq library -- not so much
> MM> to remove the 'constness' property of the PGResult. I have no
> MM> philosophical objection to making the PGresult able to be manipulated
> MM> in that fashion (although others might).
>
> From this point of view why we have PQmakeEmptyPGresult, PQcopyResult,
> PQsetResultAttrs, PQsetvalue and PQresultAlloc? If we have these
> functions I suppose we must have one more to delete (or hide) some
> tuples/attributes.
These functions were basically supported for libpqtypes -- a libpq
wrapping library that needed to be able to construct a result outside
of libpq...libpqtypes uses the result api to expose arrays and
composite types sent over the wire from the server. However, once
generated the result is basically immutable.
merlin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: mmoncure@gmail.com, pavel@gf.microolap.com, pgsql-hackers@postgresql.org
Subject: Re: PQdeleteTuple function in libpq
In-Reply-To: <BANLkTikCxdeBsEBbWOLQXSkLXnuMRVqPug@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox