Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 15:03:14 +0100] rev 8791
[req] drop pre-3.7 api on request
Dropping of API deprecated since 3.7 decided in #2772958
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 14:46:55 +0100] rev 8790
[session] drop pre-3.7 api on session
Dropping of API deprecated since 3.7 decided in #2772958
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 16:35:18 +0100] rev 8789
[transaction] use set operation in the hook control code
We use direct operator on set instead of looping by hand, This simplify the
codes.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 16:08:48 +0100] rev 8788
[session/transaction] move hook management in transaction itself
This is transaction level code.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 15:28:18 +0100] rev 8787
[session] allow writable tx_attr and use it for commit_state
This keep clarifying the code.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 16:12:39 +0100] rev 8786
[session/transaction] move add operation in session code
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 16:13:34 +0100] rev 8785
[session/transaction] move entity life utility on transaction
This access transaction related data and therefor should live in transaction.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 16:20:25 +0100] rev 8784
[transaction] small simplification in ecache code
A single assignation is simpler.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 14:16:16 +0100] rev 8783
[session/transaction] move entity cache management on session
A new utility method is added for that. It is similar to the one used for
attribute access. code is copy pasted as his. Function documentation is added.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 14:17:31 +0100] rev 8782
[session] have a nice helper function to forward access to session
This allows a lighter and clearer code. This will also ease the addition of
deprecation warning in the future.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 12:41:13 +0100] rev 8781
[session] drop dead code
session._tx is never None. New transaction are created if necessary.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 20:14:08 +0100] rev 8780
[session] use tx.data directly in session code.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 20:11:17 +0100] rev 8779
[transaction] rename transaction_data to data
Transaction.transaction_data is redundant. A transaction_data property is left
for backward compatibility. Deprecation mechanism will come in later changeset
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 19:58:43 +0100] rev 8778
[session] document Session._tx
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 20:05:49 +0100] rev 8777
[session] split session creation from default session assignation
This is the first step for more independence for Transaction.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 20:04:43 +0100] rev 8776
[session] make session lock reentrant
We are going to use it for other session related business. It is renamed from
_closed_lock to _lock in the same move.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 19:51:50 +0100] rev 8775
[session] document set_tx
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 19:49:57 +0100] rev 8774
[session] rename txstore variable to tx
This is a more accurate name
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 20:10:19 +0100] rev 8773
[session] rename `_threaddata` to `_tx`
The returned object is a Transaction object.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 19:37:51 +0100] rev 8772
[session] rename self.__threaddata.txdata to self.__threaddata.tx
This is Transaction object now.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 19:42:33 +0100] rev 8771
[session] rename _tx_data into _txs
The object inside are now Transaction object. Not TransactionData object.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 19:32:25 +0100] rev 8770
[transaction] relocate method building transaction context manager
It is in the middle of methods going to be refactored.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 18:49:48 +0100] rev 8769
[transaction] move RQLRewriter in Transaction
This remove the last ``AttributeError`` magic. The ``RQLRewriter`` needs a Session. Its
reset is handled in ``Session`` code to handle that
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 18:38:56 +0100] rev 8768
[transaction] initialize security control attribute in Transaction
There is no reason to not initialize them in __init__ time. This simplify the
Session code.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 18:33:53 +0100] rev 8767
[session] move security constant out of the class
There is no reason for it to not be global. This will ease it use by
``Transaction object``.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 18:27:34 +0100] rev 8766
[transaction] initialize hook control attribute in Transaction
There is no reason to not initialize them in __init__ time. this simplify the
transaction code.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 18:34:04 +0100] rev 8765
[session] Move hook control constants out of the class
There is no reason for them to not be global. This will ease they use by
Transaction object.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Mon, 25 Mar 2013 14:20:10 +0100] rev 8764
[transaction] initialize transaction data and state related attribute.
There is not reason to not explicitly declare and initialize attribute in
Transaction.__init__. This change requires the introduction of a
Transaction.clear() method to get ride of some wicked ``AttributeError`` based
logic.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 18:51:03 +0100] rev 8763
[transaction] handle ``mode`` default value in Transaction
The transaction mode is now explicitly passed at creation time and always read
from the Transaction object.
Note that there is a slight behavior change. The transaction mode is now set at
the creation of the transaction. Changes made to the default value have no
longer any effect on existing transaction.
Pierre-Yves David <pierre-yves.david@logilab.fr> [Fri, 22 Mar 2013 17:47:45 +0100] rev 8762
[transaction] explicit Transaction cnxset attribute
The Transaction object have a lot more attribute that those previously declared
in __init__. They are just dynamically assigned in Session code.
This changeset explicit the ``cnxset`` and ``mode`` attribute declaration.