Date index for Mar 2003

At 12.10 14/03/2003 +0100, you wrote:
> At 17.34 13/03/2003 +0100, you wrote:
>
> Problem solved, but first, let me explain why this is a bug, IMHO:
> ...
> Your opinion: is this the right way to accomplish this task?

sorry, this is not completely correct since node sub-elements (phases for 
project, for instance) are updated in the db before the update of the 
original node, hence when saving this node nothing has changed... ARGH...

Maybe the only solution is to add a global variable that is set to TRUE 
after an update of any sub-element...

I'm really getting desperate! ;P

P.