From: | Denis Laxalde <denis(dot)laxalde(at)dalibo(dot)com> |
---|---|
To: | psycopg(at)lists(dot)postgresql(dot)org |
Subject: | Re: Executing on the connection? |
Date: | 2020-12-08 13:51:06 |
Message-ID: | 7171e07d-bb96-dfc6-47e9-351d85f4a973@dalibo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
Daniele Varrazzo a écrit :
> On Wed, 2 Dec 2020 at 11:20, Daniele Varrazzo
> <daniele(dot)varrazzo(at)gmail(dot)com> wrote:
>
>> I'm toying with the idea of adding a 'connection.execute(query,
>> [params])' methd, which would basically just create a cursor
>> internally, query on it, and return it. No parameter could be passed
>> to the cursor() call, so it could only create the most standard,
>> client-side cursor (or whatever the default for the connection is, if
>> there is some form of cursor_factory, which hasn't been implemented in
>> psycopg3 yet). For anything more fancy, cursor() should be called
>> explicitly.
>
> This is what I've pushed earlier:
>
> https://www.psycopg.org/psycopg3/docs/connection.html#psycopg3.Connection.execute
>
It did not strike me earlier, but it looks a bit weird to have
connection.execute() return a "cursor" to read results while this
"cursor" can also be used to execute commands. So, perhaps, another
object, with only the interface for result retrieval would be more
appropriate?
Otherwise, that's a very nice addition, thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-12-08 14:44:56 | Re: Executing on the connection? |
Previous Message | Daniele Varrazzo | 2020-12-08 13:16:24 | Re: Executing on the connection? |