Thu, 03 Dec 2009 09:56:28 +0100 this constraint is actually unusable in yams schema for cw stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 03 Dec 2009 09:56:28 +0100] rev 3980
this constraint is actually unusable in yams schema for cw
Thu, 03 Dec 2009 09:56:15 +0100 unused since a long time now stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 03 Dec 2009 09:56:15 +0100] rev 3979
unused since a long time now
Thu, 03 Dec 2009 09:55:18 +0100 finish yesterday work on rql constraints: stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Thu, 03 Dec 2009 09:55:18 +0100] rev 3978
finish yesterday work on rql constraints: * Fix inheritance pb: there are some places where we filter constraints according to the class hierarchy, so rql unique constraint should'nt be neither a RQLContraint nor a RQLVocabularyConstraint subclass. Added test in unittest_schema reflecting this. * So now we have to get explicitly RQLUniqueConstraint where desired (eg in server/hooks.py) * Update i18ncubicweb command to include constraint types in generated pot file (this should have been there for a while...) * Update unittest_schemaserial which has been broken when serializing format for rql constraints has changed
Wed, 02 Dec 2009 18:36:16 +0100 synchronize rdef where unique constraints have been updated/added stable
Sylvain Thénault <sylvain.thenault@logilab.fr> [Wed, 02 Dec 2009 18:36:16 +0100] rev 3977
synchronize rdef where unique constraints have been updated/added
(0) -3000 -1000 -300 -100 -30 -10 -4 +4 +10 +30 +100 +300 +1000 +3000 tip