[google-appengine] Re: DB Model for a tree

2009-06-10 Thread Nick Johnson (Google)
Hi Ben, You have two options here, either of which would appear to suit your situation very well: 1) Use App Engine's built in support for parent entities and entity groups. When creating a node, pass the parent= argument to the constructor, passing the key or model instance of the parent node. A

[google-appengine] Re: DB Model for a tree

2009-06-08 Thread Ben FS
Hi Nick, I'm faced with a similar question as the original poster and can provide additional details on the nature of the tree and operations in my case, as you request below. I'm hoping this will make it possible for you to help me out. Yes, I would like tree modifications to be wrapped in trans

[google-appengine] Re: DB Model for a tree

2009-04-28 Thread Nick Johnson
The best way to do this depends on the nature of the tree, and what sort of operations you need to do on it. If you need transaction support and will do less than about 1QPS of updates to the entire tree, you could use the datastore's built in Ancestor model - construct entities with the 'parent'