Hello, > Note I dropped the row processor from under PGresult. > Please don't put it back there.
I overlooked that. I understand it. > > This seems also can be done by the return value of > > PQsetRowProcessor() (currently void). Anyway, I provide this > > function and also change the return value of PQsetRowProcessor(). > > Note you need processorParam as well. > I think it's simpler to rely on PQgetProcessor() Hmm. Ok. > > Let me confirm the effects of this function. Is the below > > description right? > > > > - PQskipResult(conn, false) makes just following PQgetResult() to > > skip current bunch of rows and the consequent PQgetResult()'s > > gathers rows as usual. > > Yes. > > > - PQskipResult(conn, true) makes all consequent PQgetResult()'s > > to skip all the rows. Well, Is this right? > > If this is right, row processor should stay also in PGresult > > context. PQskipResult() replaces the row processor in PGconn when > > the second parameter is true, and in PGresult for false. > > No, let's keep row processor only under PGconn. Then, Should I add the stash for the row processor (and needless for param) to recall after in PGconn? regards, -- Kyotaro Horiguchi NTT Open Source Software Center -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
