Second try... Wondering if anyone has an answer to these questions. Thanks!
On Nov 14, 8:14 am, johnP <[email protected]> wrote: > My data currently on MS is organized into entities. > - For example, let's say that each Organization is it's own entity > group. > > Most of my queries are within an entity/organization. An example of a > typical query is: > - Employee.all().filter('organization =', org).filter('position =', > manager).fetch(1000) > > This same query can also be done using an ancestor query: > - Employee.all().ancestor(org_key).filter('position =', > manager).fetch(1000) > > The first version of the query does not require a custom index, but > the second version does. > > My questions: > 1. Will moving from the first version to the the second version of > the query require adding custom indexes? Or am I missing something? > 2. Clarification on Strong Consistency in HR: Is it necessary to use > the ancestor() operator, or is simply querying within an entity group > strongly consistent? My assumption has been that for queries that > must be strongly consistent, it will be necessary to migrate from the > first format to the second format (increasing the number of custom > indexes I need to carry). Is this assumption correct? -- 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.
