Re: about client-side cursors

[Christophe Pettus]

> On Feb 4, 2021, at 07:02, Denis Laxalde <denis.laxa...@dalibo.com> wrote:
> 
> If "cursor" is a real database cursor, I agree.

But it's not just CURSORs that have this behavior.  libpq allows the client to 
the send the query, and then make separate requests for each row, even without 
a database cursor; this maps almost exactly to .execute() and .fetchone().  It 
doesn't seem a good idea to guarantee forever that .execute() will *never* do 
I/O without a database-side cursor.

Having a single convenience method on the connection object that does the 
equivalent of a .execute() and a .fetchall() might be useful, though.
--
-- Christophe Pettus
   x...@thebuild.com