MIME-Version: 1.0
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>
In-Reply-To: <3BA6B9FE-9A00-4F04-9C0B-263EE4301985@thebuild.com>
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Thu, 4 Feb 2021 16:24:22 +0100
Message-ID: 
 <CA+mi_8YQrVtsL7M_=CyopyeyL3wFYTU73FQ7p6fzvZ=s56Qc9w@mail.gmail.com>
Subject: Re: about client-side cursors
To: Christophe Pettus <xof@thebuild.com>
Cc: Denis Laxalde <denis.laxalde@dalibo.com>, psycopg@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, 4 Feb 2021 at 16:17, Christophe Pettus <xof@thebuild.com> wrote:

> Having a single convenience method on the connection object that does the equivalent of a .execute() and a .fetchall() might be useful, though.

You can already do it (in psycopg3):

    for record in conn.execute("query"):
        # do stuff

or

    records = conn.execute("query").fetchall()

or

    record = conn.execute("query").fetchone()

The latter examples are two methods, not one, but I think they compose
nicely enough, no? They are pretty orthogonal.


-- Daniele