Re: Changing set_session implementation

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
Cc: "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org>
Subject: Re: Changing set_session implementation
Date: 2017-02-08 10:47:40
Message-ID: 47351301-2F3E-4FA5-B791-D9C8B29ACCAE@thebuild.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: psycopg

Great work!

> On Feb 4, 2017, at 08:33, Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> wrote:
> - conn.isolation_level doesn't read the value from the server anymore
> but will return a value stored in the Python connection object by the
> user. The default value is the new ISOLATION_LEVEL_DEFAULT, meaning
> "begin a transaction, but use whatever isolation level the server is
> configured for".

Just to clarify, is this also now the default for starting a new transaction (i.e., it won't send a SET ISOLATION LEVEL across by default)?

--
-- Christophe Pettus
xof(at)thebuild(dot)com

In response to

Responses

Browse psycopg by date

  From Date Subject
Next Message Daniele Varrazzo 2017-02-08 13:35:21 Re: Changing set_session implementation
Previous Message Daniele Varrazzo 2017-02-04 16:33:13 Changing set_session implementation