[schema sync] we don't want to react on after_update_entity, it may only causes bug. CWUniqueConstraint should be deleted then a fresh one readded on change (as we do in sync_schema_props_perms) stable
authorSylvain Thénault <sylvain.thenault@logilab.fr>
Fri, 18 Feb 2011 16:30:02 +0100
branchstable
changeset 7021 fc7ac3409b0c
parent 7014 7e3e80f4179a
child 7025 fee3a1f28ed7
child 7026 2c65dd2cbfff
[schema sync] we don't want to react on after_update_entity, it may only causes bug. CWUniqueConstraint should be deleted then a fresh one readded on change (as we do in sync_schema_props_perms)
hooks/syncschema.py
--- a/hooks/syncschema.py	Fri Feb 18 09:33:32 2011 +0100
+++ b/hooks/syncschema.py	Fri Feb 18 16:30:02 2011 +0100
@@ -1127,7 +1127,7 @@
 class AfterAddCWUniqueTogetherConstraintHook(SyncSchemaHook):
     __regid__ = 'syncadd_cwuniquetogether_constraint'
     __select__ = SyncSchemaHook.__select__ & is_instance('CWUniqueTogetherConstraint')
-    events = ('after_add_entity', 'after_update_entity')
+    events = ('after_add_entity',)
 
     def __call__(self):
         CWUniqueTogetherConstraintAddOp(self._cw, entity=self.entity)