Hey Kenneth, If the data is always segregated by user, use namespaces. Put each user in their own namespace and set it in your request setup logic. Then you won't need to filter on user, it will be done implicitly.
http://code.google.com/appengine/docs/python/multitenancy/ Robert On Friday, August 26, 2011, 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 view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/MxxGtqJOxJUJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected] < google-appengine%[email protected]>. > For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en. > -- ------ Robert Kluin Ezox Systems, LLC -- 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.
