> On Feb 4, 2021, at 03:16, Denis Laxalde <[email protected]> wrote: > But, unless I missed it, the PEP does not state how to implement query > execution and result fetch operations if the database does not need a > cursor. First, any change like this would have to maintain their current API essentially forever, unless psycopg3 represents a completely incompatible break with the psycopg2 interface. There is an enormous body of code out there that uses the current cursor() interface for client-side cursors. Second, it would be very unwise to make guarantees about when these operations interact with the database. I think that any client application should expect that both cursor.execute() and cursor.fetchone()/.fetchall() are asynchronous operations, and code appropriately. -- -- Christophe Pettus [email protected]
- about client-side cursors Denis Laxalde
- Re: about client-side cursors Christophe Pettus
- Re: about client-side cursors Karsten Hilbert
- Re: about client-side cursors Christophe Pettus
- Re: about client-side cursors Daniele Varrazzo
- Re: about client-side cursors Daniele Varrazzo
- Re: about client-side cursors Denis Laxalde
- Re: about client-side cursors Christophe Pettus
- Re: about client-side cursors Denis Laxalde
- Re: about client-side cursors Christophe Pettus
- Re: about client-side cursors Daniele Varrazzo
- Re: about client-side cursors Denis Laxalde
- Re: about client-side curs... Christophe Pettus
- Re: about client-side cursors Daniele Varrazzo
- Re: about client-side cursors Denis Laxalde
- Re: about client-side cursors Christophe Pettus
- Re: about client-side cursors Denis Laxalde
- Re: about client-side cursors Karsten Hilbert
