Andrew Chernow <[EMAIL PROTECTED]> writes:
> PGresult *PQresultDup(
> PGconn *conn,
> PGresult *res,
> int ntups,
> int numAttributes,
> PGresAttDesc *attDescs);
I don't understand why this is a "dup" operation. How can you "dup"
if you are specifying a new tuple descriptor? I'd have expected
something like
PGresult *PQmakeResult(PGconn *conn, int numAttributes, PGresAttDesc *attDescs)
producing a zero-row PGRES_TUPLES_OK result that you can then load with
data via PQresultSetFieldValue calls. (Even the conn argument is a bit
of a wart, but I think we probably need it so we can copy some of its
private fields.)
Copying an existing PGresult might have some use too, but surely that
can't change its tuple descriptor.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
