Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Fri, 19 Mar 2010 19:25:53 +0100] rev 4966
[registry] trigger reload events on set_schema()
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Fri, 19 Mar 2010 19:24:34 +0100] rev 4965
[source] only consider edited_attributes in source.preprocess_entity()
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Fri, 19 Mar 2010 19:21:31 +0100] rev 4964
[source] implement storages right in the source rather than in hooks
The problem is that Storage objects will most probably change entity's
dictionary so that values are correctly set before the source's
corresponding method (e.g. entity_added()) is called.
For instance, the BFSFileStorage will change the original binary
data and replace it with the destination file path in order to store
the file path in the database. This change must be local
to the source in order not to impact other hooks or attribute access
during the transaction, the whole idea being that the same
application code should work exactly the same whether or not a
BFSStorage is used or not.
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 15:27:45 +0100] rev 4963
i18n update
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 14:47:34 +0100] rev 4962
3.7.1
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 14:47:09 +0100] rev 4961
backport stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 14:43:49 +0100] rev 4960
[etwist] cleanup, use cProfile instead of hotshot
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 14:43:15 +0100] rev 4959
[repo] start looping task on repo only config (though I bet more work is needed to get it actually working
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 14:42:35 +0100] rev 4958
[repo] call server_startup event in start_looping_task the repo is fully started (registered in pyro for instance)
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 10:10:18 +0100] rev 4957
[security] take care uidrels may contains a relation targetting something else than a constant node (eg IN function)
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 10:07:30 +0100] rev 4956
[ms] this test is already done before putting a relation in uidrels
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 09:08:09 +0100] rev 4955
cleanup
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 09:08:00 +0100] rev 4954
[security] experimental rqlst cache for read security: to activate using a 'security-rqlst-cache' flag in transaction data when you'll issue a lot of identic queries with only kwargs varying
Sylvain Thénault <sylvain.thenault@logilab.fr> [Fri, 19 Mar 2010 08:18:31 +0100] rev 4953
[read security] minor optimizations