Wed, 31 Mar 2010 14:55:54 +0200 3.7.3 stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 14:55:54 +0200] rev 5117
3.7.3
Wed, 31 Mar 2010 14:50:30 +0200 [hooks] better message on bad .event class attribute stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 14:50:30 +0200] rev 5116
[hooks] better message on bad .event class attribute
Wed, 31 Mar 2010 14:46:04 +0200 [repository] forbid usage of set_attributes() in before_add_entity stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 31 Mar 2010 14:46:04 +0200] rev 5115
[repository] forbid usage of set_attributes() in before_add_entity set_attributes() will generate a RQL query that will silently fail. An explicit error is better. You can still use the ``entity[attr] = value`` notation that won't generate a SQL query but still update the inner state of the entity and its edited_attributes attribute.
(0) -3000 -1000 -300 -100 -30 -10 -3 +3 +10 +30 +100 +300 +1000 +3000 tip