On Wed, 3 Feb 2021 at 18:44, Daniele Varrazzo
wrote:
> 2) if we want to have sync and async cursor, it would be better if
> they had the same interface
Sorry, this should have been "if we want to have client and server
cursors, it would be better if they had the same interface".
> On Feb 3, 2021, at 09:41, Karsten Hilbert wrote:
> Perhaps client-side cursors were invented to make it possible
> to code to the same API regardless of whether real
> (server-side) cursors are used or not ?
That's definitely part of it.
The name "cursor" for the client-side object is a bit
On Wed, 3 Feb 2021 at 17:16, Denis Laxalde wrote:
> I'd like to discuss about the concept of client-side cursor as defined
> in psycopg.
Welcome Denis!
> This is a concept I've always been quite uncomfortable with;
> I'll try to explain why.
>
> First, from a practical point of view:
>
>cu
Am Wed, Feb 03, 2021 at 08:27:49AM -0800 schrieb Christophe Pettus:
> > All in all, my main point is: (why) do we need client-side cursors?
>
> Well, the original source is:
>
> https://www.python.org/dev/peps/pep-0249/
>
> There are many arguments that can be made against this API, but I th
> On Feb 3, 2021, at 08:15, Denis Laxalde wrote:
>
> All in all, my main point is: (why) do we need client-side cursors?
Well, the original source is:
https://www.python.org/dev/peps/pep-0249/
There are many arguments that can be made against this API, but I think we're a
bit stuck
Hi,
I'd like to discuss about the concept of client-side cursor as defined
in psycopg. This is a concept I've always been quite uncomfortable with;
I'll try to explain why.
First, from a practical point of view:
cur = connection.cursor()
cur.execute(...)
result = cur.fetchxxx()
This ty
