[Chandler-dev] Recurrence and changes to masters in the dashboard

[Andi Vajda]

On Thu, 25 Jan 2007, Jeffrey Harris wrote:

> Intriguingly, until Andi's chandlerdb update today, you could see the
> same problem if you changed the title of all recurring events, but that
> problem appears to be fixed.

If you're referring to the yet-to-be checked in chandlerdb 0.6-78 
(chandler/Makefile, that is) that appears to fix bug 7895, the change is as 
follows.

Before the change, the order of reaction-to-change invocations was:
   1. afterChange methods
   2. monitors
   3. watchers

With this change, the order now is:
   1. system monitors (maintaining indexes, for example)
   2. afterChange methods
   3. user monitors (not sure if we have any in Chandler at the moment)
   4. watchers

This change makes sure that afterChange methods work with consistent indexes.

Andi..