| From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
|---|---|
| To: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>, Paolo De Stefani <paolo(at)paolodestefani(dot)it>, Psycopg <psycopg(at)postgresql(dot)org> |
| Subject: | Re: psycopg3 transactions |
| Date: | 2021-10-16 22:58:48 |
| Message-ID: | YWtZKL1nVM/KV5S7@hermes.hilbert.loc |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
Am Sun, Oct 17, 2021 at 12:48:40AM +0200 schrieb Karsten Hilbert:
> > https://www.psycopg.org/psycopg3/docs/basic/transactions.html
>
> I am sorry to say this but this concept:
>
> This way we don’t have to remember to call neither
> close() nor commit() and the database operation have
> actually a persistent effect.
>
> seems fundamentally flawed to me in terms of databases.
> Actually changing the content of a database should be a
> conscious decision by program(mer) logic.
I could, perhaps, agree with the *transaction* context
manager being default-commit because:
- after the context block the transaction has gone away
- hence what happens inside either failed (auto-rollback)
- or is to be committed
Not so for the *connection* context manager.
Best,
Karsten
--
GPG 40BE 5B0E C98E 1713 AFA6 5BC0 3BEA AC80 7D4F C89B
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-10-20 20:07:13 | Re: psycopg3 transactions |
| Previous Message | Karsten Hilbert | 2021-10-16 22:48:40 | Re: psycopg3 transactions |