Also: http://code.google.com/appengine/docs/python/datastore/queries.html#Big_Entities_and_Exploding_Indexes
On Aug 26, 12:16 am, Kenneth <[email protected]> wrote: > I have a model with say 10 properties. The user can filter on any of these > properties to view a list. The list is also always filtered on the user. > This means there is a composite index for each one of the properties that > the user can filter on to start with, but then there also needs to a > composite index for every combination of filters, including a filter on all > 10 properties. That's a lot of indexes. > > The only solution I can think of is if the user picks more than 2 filter > criteria then I do the filtering on the client side as the data set should > have been reduced sufficiently so there isn't too much data. > > Anyone else run into this problem and have any insights? -- 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.
