From: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Re: Changing set_session implementation |
Date: | 2017-08-02 15:02:28 |
Message-ID: | 20170802150228.lf6niwsvnaqmjr2p@hermes.hilbert.loc |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On Wed, Aug 02, 2017 at 03:10:15PM +0100, Daniele Varrazzo wrote:
> Hi Karsten, sorry for the late reply,
No problem, thanks.
> no, `conn.set_isolation_level(ISOLATION_LEVEL_AUTOCOMMIT)` is not a no-op:
>
> In [1]: import psycopg2
>
> In [2]: psycopg2.__version__
> Out[2]: '2.7.3 (dt dec pq3 ext lo64)'
>
> In [3]: cnn = psycopg2.connect('')
>
> In [4]: cnn.autocommit
> Out[4]: False
>
> In [5]: cnn.set_isolation_level(psycopg2.extensions.ISOLATION_LEVEL_AUTOCOMMIT)
>
> In [6]: cnn.autocommit
> Out[6]: True
I see. I thought as much. Put another way,
cnn.set_isolation_level(psycopg2.extensions.ISOLATION_LEVEL_AUTOCOMMIT)
and
cnn.set_session(autocommit = True)
do the same thing.
Thanks,
Karsten
--
GPG key ID E4071346 @ eu.pool.sks-keyservers.net
E167 67FD A291 2BEA 73BD 4537 78B9 A9F9 E407 1346
From | Date | Subject | |
---|---|---|---|
Next Message | Karsten Hilbert | 2017-08-02 19:38:21 | Re: Changing set_session implementation |
Previous Message | Daniele Varrazzo | 2017-08-02 14:10:15 | Re: Changing set_session implementation |