Here is the approach I would probably take unless you have many
hundreds of child tasks.
I would keep a list of keys of all children of each project/task.
(You can then do a db.get and get all immediate children with single
call)
and each child has a reference to it's parent. In addition in each
item keep a list of all parents keys back to the root. That way you
can search for all children
in part of the tree/subtree
(This approach is especially useful if you have multiple child types)
as back ref sets
are kind specific.
Keep a running count of complete children at each level, rather than
trying to calculate the current state in a single big function, (keep
these subsidiary values up to date through tasks)
AppEngine JDO example #1: retrieve an object by ID « TurboManage - 0 views
Gist - GitHub - 0 views
Kinds, Names and IDs (Slim3) - 0 views
DatastoreService - 0 views
App Engine Fan: Schluesselmeister - 0 views
Jeremy's Blog: Simple Google Gadget on GAE - 0 views
« First
‹ Previous
221 - 240 of 592
Next ›
Last »
Showing 20▼ items per page