Is there any reason to use an Entity Group in Google Datastore other than for enabling transactions?
For example, does having entities in the same entity group speed up queries? The situation that I run into often is whether to have X be a parent to Y or have X be a property of Y. Both cases allow for Y to be queried given X, but when transactions aren't needed perhaps the entity group is not necessary. I guess another way of stating the question is whether or not ancestor queries provide speed up over property based queries without ancestors? -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/846d1d10-af2c-4c9a-80eb-bf29708017da%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
