update, insert, delete and deleteby methods can generate events, either before or after execution, or both. To activate event dispatching, you have to declare which events your application want to catch in the events attribute of the <factory> element. Event names are separated by a comma. Full event list includes: deletebefore, deleteafter, updatebefore, updateafter, insertbefore, insertafter, deletebybefore, deletebyafter.

Below is a detailed list of each event and its parameters. Every event has a dao parameter corresponding to their dao selector.

• daoDeleteBefore : key (key values of the to be deleted record)
• daoDeleteAfter : key, result (1 if record is truely deleted)
• daoDeleteByBefore : key, criterias (objet jDaoConditions)
• daoDeleteByAfter : key, criterias, result (number of deleted records)
• daoUpdateBefore : record (to be updated record object)
• daoUpdateAfter : record
• daoInsertBefore : record (to be inserted record object)
• daoInsertAfter : record

Here an example.

Dao file ¶

  <factory events="deleteAfter, insertAfter"> ...

Listener ¶

class myListener extends jEventListener{
 
   function onDaoDeleteAfter ($event) {
        $dao = $event->getParam('dao');
        if ($dao == 'mymodule~thedao') {
            $keys = $event->getParam('keys');
            //...
        }
   }

$event->getParam("record")->myPropriety = $Variable;

events.xml ¶

<events xmlns="http://jelix.org/ns/events/1.0">
   <listener name="my">
       <event name="daoInsertAfter" />
       <event name="daoDeleteAfter" />
   </listener>
</events>

Customized update or delete methods (XML or PHP methods) can declare eventbefore and/or eventafter attributes and set them to true or false.

Generated events will be: daoSpecificUpdateBefore, daoSpecificUpdateAfter, daoSpecificDeleteBefore et daoSpecificDeleteAfter.

They will be emitted with those parameters:

• dao: dao selector
• method: method name
• params: parameters list