| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Reuben Rissler <silrep(at)emypeople(dot)net> |
| Cc: | psycopg(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Nested transactions support for code composability |
| Date: | 2020-02-15 20:55:08 |
| Message-ID: | 845278C0-2D5F-4B2C-8DEF-D952349933D1@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
> On Feb 15, 2020, at 10:24, Reuben Rissler <silrep(at)emypeople(dot)net> wrote:
> 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.
This has been implemented by the Django atomic() context manager for quite some time, in fact.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniele Varrazzo | 2020-02-16 11:52:29 | Re: Nested transactions support for code composability |
| Previous Message | Daniel Fortunov | 2020-02-15 19:38:32 | Nested transactions support for code composability |