On Fri, Jan 6, 2012 at 7:47 AM, Richard Watson <[email protected]> wrote: > What if you had the gps data as children of each entry and then used a > keys-only query to match, and then fetch the parents. I forget the > technique's name, maybe someone else remembers. The benefit is that when > you need to edit gps coords you leave the parent alone. Data in the parent > isn't duplicated and all changes only happen to the children. No parent data > is re-indexed so you reduce datastore charges on updates. I'm not 100% sure > it'd help but it might be worth testing.
This shouldn't help. Re-puting an entity won't cause index updates if the indexed values don't change. The "relation index entity" pattern is only useful when you have very large #s of index items (many thousands). You wouldn't want to do it for 20 short strings. Jeff -- 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.
