How about updating all ancestors on task status change? That way you wouldn't need to find all the children.
On Sun, Apr 18, 2010 at 2:29 PM, gops <[email protected]> wrote: > hi , i am designing a simple project based to do list. the idea is to > define tasks under project ( no workflow - just "task is completed" or > not is required. ) in a hirarchial way. i.e. each task has multiple > task and that task may have other multiple task. a project can be said > to be completed if all task under that project are completed. , i > tought of using refrenceproeperty to create hirarchy , but could not > figure out easy way ( which do not take more than 30 seconds to find > all the children of a project and check weather it is completed or > not ) . to detect if project is complete or not. how to design > database for such job ? and also , if i need to copy the project in > order to define another project , how to copy hierarchical data ? > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
