if you use slim3 for your data store operations you can avoid all this parenting nonsense. slim3 allows you to update two of the same kind in a single transaction! why should we be required to place entities that are not logically related into a parenting relationship just to get transaction support?
I have a game where a user domain object has a list of friends (users). Try modeling that as a parent relationship. It's self-referential. A user is not a parent of another user. Then try adding a list of games domain objects, and add a new friend to a new game in a single transaction. With stand-alone domain objects it's simple. Back to the original post.... I'm finding the latency on the master/slave datastore is too unpredictable for my game. Hopefully migrating will eliminate some of the long latency, and dynamic instance start problems i'm seeing. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/1zQr36sv23sJ. 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.
