> However, when I do this, the dev_server creates a bunch of index > definitions, so that I have one with 1 property if there's 1 value in > the IN set, 15 index properties if there are 15 values in the IN set, > and so on.
Are all of these index properties necessary in production? Will a production query with an IN set with 4 members fail if the test set used to generate index.yaml has IN sets with 1, 3, and 5 members? On Feb 28, 4:55 pm, Devel63 <danstic...@gmail.com> wrote: > I understand that if you issue a query using "IN", the datastore > actually issues as many sub-queries as there are values listed in the > IN set, up to a max of 30. It's not the greatest, but I get it. > > However, when I do this, the dev_server creates a bunch of index > definitions, so that I have one with 1 property if there's 1 value in > the IN set, 15 index properties if there are 15 values in the IN set, > and so on. > > This doesn't seem to be scalable, especially if there are other > variations of property conditions in the mix. Should I just do the > looping outside the query, and ask for an equality with each value in > the IN set? Are these index definitions really indicative of what > will need to happen on the server? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
