Kyle Gearhart <kyle.gearh...@indigohill.io> writes: > The guts of pqRowProcessor in libpq does a good bit of work to maintain the > internal data structure of a PGresult. There are a few use cases where the > caller doesn't need the ability to access the result set row by row, column > by column using PQgetvalue. Think of an ORM that is just going to copy the > data from PGresult for each row into its own structures.
It seems like you're sort of reinventing "single row mode": https://www.postgresql.org/docs/devel/static/libpq-single-row-mode.html Do we really need yet another way of breaking the unitary-query-result abstraction? 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
