Sylvain Thénault <sylvain.thenault@logilab.fr> [Tue, 23 Mar 2010 09:19:42 +0100] rev 4971
don't use optional on final relation
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 22 Mar 2010 17:58:03 +0100] rev 4970
fix security issue introduced by 4967:04543ed0bbdc: attributes explicitly set by hooks should not be checked by security hooks
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 22 Mar 2010 16:33:29 +0100] rev 4969
[form js] apply vgodard patch fixing #750056: reorderTabindex js function crashes when form dom id is not 'entityForm'
Sylvain Thénault <sylvain.thenault@logilab.fr> [Mon, 22 Mar 2010 11:11:00 +0100] rev 4968
missing unittest_main
Adrien Di Mascio <Adrien.DiMascio@logilab.fr> [Sun, 21 Mar 2010 18:21:27 +0100] rev 4967
[server] add unit tests for storages
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