On Thu, Jun 2, 2011 at 3:24 AM, Pavel Golub <pa...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
