MIME-Version: 1.0
References: 
 <CA+mi_8Yc92bX3qhTqXq4LkGyn5VmQj6uRAcVebpqt398Tm4EJA@mail.gmail.com>
 <b4f9f222-fc78-1930-596b-9daf05f9d43c@aklaver.com>
In-Reply-To: <b4f9f222-fc78-1930-596b-9daf05f9d43c@aklaver.com>
From: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Date: Wed, 2 Dec 2020 15:42:12 +0000
Message-ID: 
 <CA+mi_8akt_guKx_Reqrvr_U5tvy8_9qHpUV3TvyO8a4KkJnxfQ@mail.gmail.com>
Subject: Re: Executing on the connection?
To: Adrian Klaver <adrian.klaver@aklaver.com>
Cc: psycopg@postgresql.org
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Wed, 2 Dec 2020 at 15:02, Adrian Klaver <adrian.klaver@aklaver.com> wrote:

> Just to be clear the above(callproc excepted) or some variation of it
> will still be available off the cursor interface, correct?

Yes, that's correct. The cursor remains with the methods it is known
for. This Connection.execute() would only be the moral equivalent of:

    class Connection:
        def execute(self, query, params=None):
            cur = self.cursor()
            cur.execute(query, params)
            return cur

but nothing would be removed from the cursor interface.

-- Daniele