Tue, 31 Jul 2012 17:32:54 +0200 [composite] apply composite on new enty too (closes #2450679) oldstable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 17:32:54 +0200] rev 8502
[composite] apply composite on new enty too (closes #2450679) Before this changesets, automatic deletion did not applied to entity created in the same transaction. This patch remove this filtering in the dedicated operation. The original filtering where introduced by 5d889b4928bb but no rational where found for this changes. The former behavior is seen as inconsistent and creates bug in some cubes.
Tue, 31 Jul 2012 17:25:28 +0200 [storage] relies on event=='deleted' to detect "delete" event (closes #2450680) oldstable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 17:25:28 +0200] rev 8501
[storage] relies on event=='deleted' to detect "delete" event (closes #2450680) When we delete a previously edited entity, it *will* have a cw_edited attribute even if the goal is to delete it. The function get an argument that explicitly contains the "delete" event. The code now uses that instead.
Tue, 31 Jul 2012 11:04:45 +0200 [composite] apply composite on new enty too stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 11:04:45 +0200] rev 8500
[composite] apply composite on new enty too Before this changesets, automatic deletion did not applied to entity created in the same transaction. This patch remove this filtering in the dedicated operation. The original filtering where introduced by 5d889b4928bb but no rational where found for this changes. The former behavior is seen as inconsistent and creates bug in some cubes.
Tue, 31 Jul 2012 10:57:03 +0200 [storage] relies on event=='deleted' to detect "delete" event stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Tue, 31 Jul 2012 10:57:03 +0200] rev 8499
[storage] relies on event=='deleted' to detect "delete" event When we delete a previously edited entity, it *will* have a cw_edited attribute even if the goal is to delete it. The function get an argument that explicitly contains the "delete" event. The code now uses that instead.
(0) -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 +3000 tip