Subject: Re: Nested transactions support for code composability
To: psycopg@lists.postgresql.org
References: 
 <CAH1rg6YS5n6PjiV=9cBr2E--oKXtUuL=S7fNPs+Y6BuwRA0iGA@mail.gmail.com>
 <CAH1rg6bzuNNcJGn94fLA2FTo08O3xxMDd-jos3g_5JEbhuTOqA@mail.gmail.com>
From: Reuben Rissler <silrep@emypeople.net>
Message-ID: <36003642-bd79-1d5a-ef2f-9d921acd299f@emypeople.net>
Date: Sat, 15 Feb 2020 13:24:19 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: 
 <CAH1rg6bzuNNcJGn94fLA2FTo08O3xxMDd-jos3g_5JEbhuTOqA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Precedence: bulk


On 02/15/2020 11:55 AM, Daniel Fortunov wrote:
>
>
> For details on the library, see the README at 
> https://github.com/asqui/psycopg-nestedtransactions
>
> Do people think this is worthy of inclusion in psycopg2.extras (or 
> elsewhere in psycopg2?)
This is interesting, to say the least. I use psycopg2 a lot, but I never 
got around to researching psycopg2 for this type of action. I can't help 
you out on how to get this into psycopg2 officially, and I don't even 
know if / when I'll use it, but it is nice to know I'm not the only one 
who has thought in patterns like this.

Reuben
>
> Thanks in advance,
> Daniel Fortunov