On Sun, Mar 18, 2018 at 01:53:20PM -0500, Justin Pryzby wrote: > I wanted to pick this up and finally finish it.. > > Some opened question in my mind: > > - should we implement real serverside cursors instead? Or is that off the > table for "classic" interface for some reason?
I don't think I initially (7 months ago) realized that I wasa implementing for pg exactly what already exists for pgdb (right?). > - Or should we implement enough of serverside cursors to be sure of what > interfaces to expose (it's easy enough, but want to avoid have two > different > interfaces). ..and now I'm glad I did, since I think I'd like to propose not exporting a Move() function at all...since the classic interface currently has no mechanism to access a single row :) The sequence protocol (getitem) will provide that, as a new feature. And if someone wants to access a specific row or range of rows, then can just loop around the needed rows, rather than iterating the query object. WDYT? Justin _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
