Re: PQdeleteTuple function in libpq
Andrew Chernow <[email protected]> Thu, 02 Jun 2011 10:33:07 -0400
| Newsgroups | gmane.comp.db.postgresql.devel.general,gmane.comp.db.postgresql.interfaces |
|---|---|
| Message-ID | <[email protected]> |
>> AC> IMHO, this should be handled by the application. You could track >> tuples >> AC> removed in an int[] or copy the result set into an application >> defined >> AC> array of C structures. I've always been under the impression that >> AC> PGresult objects are immutable once delivered to the application. >> >> >> Andrew, why we have PQmakeEmptyPGresult, PQcopyResult, >> PQsetResultAttrs, PQsetvalue and PQresultAlloc in this case? Of course >> there's no big deal with their absence but let's be consistent. >> > > I'm not entirely sure what you are trying to do, but can't you use > PQmakeEmptyPGresult, PQsetResultAttrs and PQsetvalue to construct a > result that excludes the tuples you don't want followed by a > PQclear(initial_result)? > Actually the best solution would be to call PQcopyResult with all PG_COPYRES_XXX flags enabled except PG_COPYRES_TUPLES. Now call PQsetvalue for each tuple you want to add. -- Andrew Chernow eSilo, LLC global backup http://www.esilo.com/ -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers