Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.7\))
Subject: Re: about client-side cursors
From: Christophe Pettus <xof@thebuild.com>
In-Reply-To: <20210204163852.5mwvddtr74aw6wrh@dalibo.com>
Date: Thu, 4 Feb 2021 08:44:31 -0800
Cc: Daniele Varrazzo <daniele.varrazzo@gmail.com>,
 psycopg@postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <9E627534-4E82-405E-AC6B-45D73C25989B@thebuild.com>
References: <20210203161548.vkhu3qkpvmgvyhik@dalibo.com>
 <CA+mi_8a1ery2xvb+AdxMtVXydOdGC7wRMnfXNAvk8v73HsLFyw@mail.gmail.com>
 <20210204111647.4s3qie5cnassksa5@dalibo.com>
 <BAB9FCFC-96F6-48E2-98EA-FF851AA6C884@thebuild.com>
 <20210204150203.iuophq3yx7nzpfzo@dalibo.com>
 <3BA6B9FE-9A00-4F04-9C0B-263EE4301985@thebuild.com>
 <20210204163852.5mwvddtr74aw6wrh@dalibo.com>
To: Denis Laxalde <denis.laxalde@dalibo.com>
Precedence: bulk


> On Feb 4, 2021, at 08:38, Denis Laxalde <denis.laxalde@dalibo.com> =
wrote:
> Is this related to prepared statements in the extended query protocol?
> (Then, I'd argue that both preparation and execution steps would =
involve
> IO. But if it's not a cursor, we should use a different name, as
> postgresql doc does.)

No, this is separate from prepared statements or the extended protocol.  =
You can do single-row returns with either basic or extended protocol.

It's unfortunate that cursor as become overloaded, but I think that's =
something we just have to accept at this point.  It sounds like the real =
issue is that it would be convenient to have a single async function =
that does the semantic equivalent of:

curs =3D connection.cursor()
curs.execute(query, *parameters)
for row in curs.fetchall():
   yield row
curs.close()
--
-- Christophe Pettus
   xof@thebuild.com