server/hook.py
changeset 6366 1806148d6ce8
parent 6279 42079f752a9c
parent 6345 1a7f4bfbf92b
child 6426 541659c39f6a
--- a/server/hook.py	Thu Sep 23 23:28:58 2010 +0200
+++ b/server/hook.py	Wed Sep 29 16:16:32 2010 +0200
@@ -60,6 +60,11 @@
 .. _`database trigger`: http://en.wikipedia.org/wiki/Database_trigger
 
 
+.. hint::
+
+   It is a good practice to write unit tests for each hook. See an example in
+   :ref:`hook_test`
+
 Operations
 ~~~~~~~~~~
 
@@ -402,7 +407,7 @@
 
           class MyHook(Hook):
             __regid__ = 'whatever'
-            __select__ = Hook.__select__ & implements('Person')
+            __select__ = Hook.__select__ & is_instance('Person')
 
       else your hooks will be called madly, whatever the event.
     """
@@ -490,6 +495,8 @@
 
     This hook ensure that when one of the watched relation is added, the
     `main_rtype` relation is added to the target entity of the relation.
+    Notice there are no default behaviour defined when a watched relation is
+    deleted, you'll have to handle this by yourself.
 
     You usually want to use the :class:`match_rtype_sets` selector on concret
     classes.