| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | psycopg(at)postgresql(dot)org |
| Subject: | Re: Executing on the connection? |
| Date: | 2020-12-02 15:42:12 |
| Message-ID: | CA+mi_8akt_guKx_Reqrvr_U5tvy8_9qHpUV3TvyO8a4KkJnxfQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Wed, 2 Dec 2020 at 15:02, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karsten Hilbert | 2020-12-02 16:23:01 | Re: Executing on the connection? |
| Previous Message | Adrian Klaver | 2020-12-02 15:02:28 | Re: Executing on the connection? |