Subject: Re: about client-side cursors
To: Daniele Varrazzo <daniele.varrazzo@gmail.com>
Cc: psycopg@postgresql.org
References: <20210203161548.vkhu3qkpvmgvyhik@dalibo.com>
 <CA+mi_8a4A9-fu39sLzvGbeqF9odLBNuyORfMc5K4yv=XgZQjsA@mail.gmail.com>
From: Denis Laxalde <denis.laxalde@dalibo.com>
Message-ID: <921417ec-6fc6-a622-b47f-fd5edccfd9c1@dalibo.com>
Date: Wed, 10 Feb 2021 15:46:54 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101
 Thunderbird/78.6.0
MIME-Version: 1.0
In-Reply-To: 
 <CA+mi_8a4A9-fu39sLzvGbeqF9odLBNuyORfMc5K4yv=XgZQjsA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: fr
Content-Transfer-Encoding: 8bit
Precedence: bulk

Daniele Varrazzo a écrit :
> So, in the server-side branch, I've made the function non-async on
> AsyncConnection too. This makes also context manager better to use, as
> now you can do:
> 
>      async with aconn.cursor() as cur:
>          # use it
> 
> whereas previously it would have taken an `async with await aconn.cursor()`.
> 
> I assume the change is welcome, but please let me know if this is not the case.

Yes, that change is welcome. Thanks!