Wed, 31 Mar 2010 11:52:15 +0200 Add context management methode to dbapi.Connection stable
Pierre-Yves David <pierre-yves.david@logilab.fr> [Wed, 31 Mar 2010 11:52:15 +0200] rev 5100
Add context management methode to dbapi.Connection the connection is automaticly closed when exiting the context.
Wed, 31 Mar 2010 11:41:20 +0200 i18n update stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 11:41:20 +0200] rev 5099
i18n update
Wed, 31 Mar 2010 11:41:17 +0200 [i18n] use named substitution to avoid gettext warnings stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 11:41:17 +0200] rev 5098
[i18n] use named substitution to avoid gettext warnings
Wed, 31 Mar 2010 10:56:43 +0200 [dataimport] print transaction id when we get one stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 10:56:43 +0200] rev 5097
[dataimport] print transaction id when we get one
Wed, 31 Mar 2010 09:58:44 +0200 [cleanup] add some notes stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 09:58:44 +0200] rev 5096
[cleanup] add some notes
Wed, 31 Mar 2010 09:58:20 +0200 [optimisation] _select_best is used very intensivly. Peanuts optimization may count :) stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 09:58:20 +0200] rev 5095
[optimisation] _select_best is used very intensivly. Peanuts optimization may count :)
Wed, 31 Mar 2010 09:57:18 +0200 [optimization] traced_selection is used very intensively in debug mode stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 09:57:18 +0200] rev 5094
[optimization] traced_selection is used very intensively in debug mode optimizing it is worth the pain. Basically : don't do stuff unnecessary when we don't trace anything.
Wed, 31 Mar 2010 09:55:19 +0200 [optimization] improve massive write performance by optimizing hooks selection stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 09:55:19 +0200] rev 5093
[optimization] improve massive write performance by optimizing hooks selection profiling on some massive deletion showed up that 2/3 of the time was spent in hooks selection. Those changes make it much more acceptable (through selection is still not negligeable): * use one registry for each event, so we've much less hooks to check when emiting an event as well as no more need for the match_event selector. This required ability to put one appobject into several registries, using a __registries__ class attribute. * check for deprecated .enabled at registry initialization time instead of at selection time A very simple HooksManager class has been reintroduce to choose the right registry on call_hooks. Those optimisations leads to a ~x3 factor of time necessary to delete 16000 entities.
(0) -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 tip