On Tue, 8 Dec 2020 at 13:51, Denis Laxalde wrote:
> 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
On 12/8/20 5:51 AM, Denis Laxalde wrote:
Daniele Varrazzo a écrit :
On Wed, 2 Dec 2020 at 11:20, Daniele Varrazzo
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 para
Daniele Varrazzo a écrit :
On Wed, 2 Dec 2020 at 11:20, Daniele Varrazzo
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
On Wed, 2 Dec 2020 at 11:20, Daniele Varrazzo
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 cre
