Thu, 28 Mar 2013 12:31:39 +0100 server/source/native: fix wrong usage of .lstrip that produce garbled error messages (closes #2777641) oldstable
Aurelien Campeas <aurelien.campeas@logilab.fr> [Thu, 28 Mar 2013 12:31:39 +0100] rev 8820
server/source/native: fix wrong usage of .lstrip that produce garbled error messages (closes #2777641) Fixed an .rstrip(...) for the general case (untested). Fixed an .lstrip(...) for the sqlite path (tested).
Thu, 28 Mar 2013 11:40:19 +0100 [doc] update 3.17 release note
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 28 Mar 2013 11:40:19 +0100] rev 8819
[doc] update 3.17 release note
Thu, 28 Mar 2013 11:45:17 +0100 [migration] fix bug in `CWAttributeAddOp.revertprecommit_event` oldstable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Thu, 28 Mar 2013 11:45:17 +0100] rev 8818
[migration] fix bug in `CWAttributeAddOp.revertprecommit_event` The `rdefdef` attribute is set during the operation execution. In some the operation crash before this assignment. In such case `revertprecommit` raise an attribute error crashing the whole process and shadowing the original error. This changeset detect and Avoid this situation.
Wed, 27 Mar 2013 16:41:45 +0100 [session] security context directly use transaction object when applicable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 16:41:45 +0100] rev 8817
[session] security context directly use transaction object when applicable Most of the security logic have been moved on Transaction anyway.
Wed, 27 Mar 2013 16:43:34 +0100 [session] move context manager logic in the security context manager
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 16:43:34 +0100] rev 8816
[session] move context manager logic in the security context manager The `init_security` and `reset_security` method have no other user that the context manager itself. Having dedicated public function is not useful.
Wed, 27 Mar 2013 16:42:18 +0100 [session] hook control context directly use transaction object when applicable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 16:42:18 +0100] rev 8815
[session] hook control context directly use transaction object when applicable Most of the hooks control logic have been moved on Transaction anyway.
Wed, 27 Mar 2013 16:17:21 +0100 [session] move context manager logic in the hook controls context manager
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 16:17:21 +0100] rev 8814
[session] move context manager logic in the hook controls context manager The `init_hooks_mode_categories` and `reset_hooks_mode_categories` have no other user that the context manager itself. Having dedicated public function is not useful.
Wed, 27 Mar 2013 14:05:14 +0100 [session] drop the useless set_hooks_mode method
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 14:05:14 +0100] rev 8813
[session] drop the useless set_hooks_mode method It has not external user and trivial code
Wed, 27 Mar 2013 17:09:55 +0100 [session/transaction] move most undo support into transaction
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 17:09:55 +0100] rev 8812
[session/transaction] move most undo support into transaction A small part that need repo access has not been moved into transaction yet.
Wed, 27 Mar 2013 11:42:13 +0100 [session] simplify mode property
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 27 Mar 2013 11:42:13 +0100] rev 8811
[session] simplify mode property We can delegate very thing to transaction utility
(0) -3000 -1000 -300 -100 -10 +10 +100 +300 +1000 +3000 tip