Mon, 29 Mar 2010 13:34:24 +0200 [cleanup] stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 29 Mar 2010 13:34:24 +0200] rev 5061
[cleanup]
Mon, 29 Mar 2010 13:34:06 +0200 [repo] optimize massive insertion/deletion by using the new set_operation function stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 29 Mar 2010 13:34:06 +0200] rev 5060
[repo] optimize massive insertion/deletion by using the new set_operation function Idea is that on massive insertion, cost of handling the list of operation become non negligeable, so we should minimize the number of operations in that list. The set_operation function ease usage of operation associated to data in session.transaction_data, and we only add the operation when data set isn't initialized yet, else we simply add data to the set. The operation then simply process accumulated data.
Mon, 29 Mar 2010 13:28:41 +0200 [repo] make etype which should go in deleted_entities configurable: we only need this for types imported from other multi-sources instances stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 29 Mar 2010 13:28:41 +0200] rev 5059
[repo] make etype which should go in deleted_entities configurable: we only need this for types imported from other multi-sources instances
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 tip