On Sun, Apr 22, 2018 at 02:01:59PM +0200, Christoph Zwerschke wrote: > Am 26.03.2018 um 22:01 schrieb Justin Pryzby: > > I have one patch ready for evaluation. > > > > 1: implement fake/pseudo cursors in pg (same as what's in pgdb); > > I proposed not to support any "move()" function in pg, since > > there's no "fetch" (besides getItem which is newly introduced > > at your suggestion). This patch is solid. > > > > I also have additional patches which are "in progress" and less > > solid. I'll prepare after you after your evaluation of (1). > > > * I don't think max_row and num_fields should be stored in the queryObject, > since they can easily be accessed as PQntuples(obj->result) and > PQnfields(obj->result), which is actually only a cheap lookup. Better to > have a single source of truth only. Storing col_types might be reasonable, > but:
Note that the reason this is done this way is because that's what's needed for "server cursors", for which len/ntuples requires running "MOVE FORWARD ALL" during .query(), even if .getresult et al are never called. In that case, it doesn't make sense not to save it and saving that result -- Justin Pryzby System Administrator Telsasoft +1-952-707-8581 _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
