Fri, 22 Mar 2013 20:10:19 +0100 [session] rename `_threaddata` to `_tx`
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.
Fri, 22 Mar 2013 19:37:51 +0100 [session] rename self.__threaddata.txdata to self.__threaddata.tx
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.
Fri, 22 Mar 2013 19:42:33 +0100 [session] rename _tx_data into _txs
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.
Fri, 22 Mar 2013 19:32:25 +0100 [transaction] relocate method building transaction context manager
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.
Fri, 22 Mar 2013 18:49:48 +0100 [transaction] move RQLRewriter in Transaction
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
Fri, 22 Mar 2013 18:38:56 +0100 [transaction] initialize security control attribute in Transaction
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.
Fri, 22 Mar 2013 18:33:53 +0100 [session] move security constant out of the class
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``.
Fri, 22 Mar 2013 18:27:34 +0100 [transaction] initialize hook control attribute in Transaction
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.
Fri, 22 Mar 2013 18:34:04 +0100 [session] Move hook control constants out of the class
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.
Mon, 25 Mar 2013 14:20:10 +0100 [transaction] initialize transaction data and state related attribute.
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.
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip