| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Daniel Fortunov <psycopg-list(at)danielfortunov(dot)com> |
| Cc: | psycopg(at)postgresql(dot)org |
| Subject: | Re: Nested transactions support for code composability |
| Date: | 2017-01-22 17:22:49 |
| Message-ID: | 52454DD0-5286-451C-8502-DA8C21ED3056@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
> On Jan 22, 2017, at 08:49, Daniel Fortunov <psycopg-list(at)danielfortunov(dot)com> wrote:
> So what am I missing? Doesn't anyone find the need for this outside of Django?!
Mostly, it's that relatively few people use raw psycopg2 for database access in substantial applications; they all use some kind of framework (SQL Alchemy, Django) that mediates between the database and application. Thus, adding this kind of "nested" transaction support has to be done in concert with the framework.
It for sure can be done outside of any framework; there's nothing all that Django specific about xact(), in particular.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2017-01-22 17:57:23 | Re: Nested transactions support for code composability |
| Previous Message | Daniel Fortunov | 2017-01-22 16:49:18 | Re: Nested transactions support for code composability |