You can do this, although since its a consistent database structure, relational links to other objects can be challenging. Hierarchy resolution gets more challenging as you walk the tree through recursion. The entity datastore works perfect for storing objects using the above method. Unowned relationships require some code overhead to make sure things stay consistent and don't get orphaned.
What I do is define my objects in a normal matter send them over RPC and then store them in the desired pattern above. I wouldn't make your rpc data objects to complicated, because after you pass about 5k of code it gets much more challenging to manage if there more complex. I think there are several ways you could attack this, but it is doable. Well, Not sure I hit the points all that well, but datastore is really flexible. I think one just has to manage the relationships to other properties and entities. Brandon Donnelson http://gwt-examples.googlecode.com -- 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.
