public inbox for [email protected]  

help / color / mirror / Atom feed

From: Reuben Rissler <[email protected]>
To: [email protected]
Subject: Re: psycopg3 transactions
Date: Wed, 13 Oct 2021 08:20:54 -0400
Message-ID: <[email protected]> (raw)
In-Reply-To: <CA+mi_8afF2jMifiLSvL99+Ztupy1me7xDNAv0g47WxHWbwN9vw@mail.gmail.com>
References: <[email protected]>
	<CA+mi_8bXjHTrzDLQ+n_6K2MHVsr0J32X1HA28Ey9O+-Zm6JaeQ@mail.gmail.com>
	<[email protected]>
	<CA+mi_8afF2jMifiLSvL99+Ztupy1me7xDNAv0g47WxHWbwN9vw@mail.gmail.com>

<snip>
> I think we can improve the documentation there by extending more about
> the effects of the interaction between DBAPI transactions and the
> transaction() blocks. And things are definitely more intuitive if
> transaction() is used in autocommit: we might want to advise people to
> do that.
>
> Suggestions are welcome.
>
> -- Daniele
>
I find this new behavior of psycopg(3) more sane, even if less 
?intuitive?, than the behavior of psycopg2. I had run across the fact 
that you can close the cursor and then commit afterwards. I found this 
odd, as I would have guessed closing a cursor with uncomitted data would 
have thrown the data away.

Disclaimer: I haven't actually used the new psycopg. I just actively 
follow this mail list while continuing to use psycopg2.


Reuben Rissler

view thread (28+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected]
  Subject: Re: psycopg3 transactions
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox