From: | Oswaldo <listas(at)soft-com(dot)es> |
---|---|
To: | psycopg(at)postgresql(dot)org |
Subject: | Re: Transaction control overhauling |
Date: | 2011-05-12 15:15:05 |
Message-ID: | 4DCBF979.5030209@soft-com.es |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
El 12/05/2011 16:07, Federico Di Gregorio escribió:
> On 12/05/11 12:36, Daniele Varrazzo wrote:
> [snip]
>>> Or,
>>> maybe even better, we can have 4 attributes and the set_transaction() as
>>> a shortcut:
>>>
>>> conn.autocommit
>>> conn.transaction_isolation_level
>>> conn.transaction_readonly
>>> conn.transaction_deferrable
>>> conn.set_transaction(isolation_level, autocommit, readonly, ...)
>>
>> Wow, I thought you wanted to limit the dbapi extensions :)
>
> Well, I know. But, in fact, if we introduce the possibility to set such
> parameters we also _need_ a way to retrieve them and attributes are the
> only sensible way to retrive them (a function returning a tuple is
> another way but stinks.)
>
Another way is setting transacion mode with predefined constants and
combining it with '|':
previous_mode = conn.set_transaction(psycppg2.TM_SERIALIZABLE |
psycppg2.TM_READONLY)
--
Oswaldo Hernández
From | Date | Subject | |
---|---|---|---|
Next Message | Federico Di Gregorio | 2011-05-12 15:47:41 | Re: Transaction control overhauling |
Previous Message | Daniele Varrazzo | 2011-05-12 14:25:53 | Re: Transaction control overhauling |