The exploding index issue can occur with list properties readily. "Properties with multiple values, such as using a list value or a ListProperty model, store each value as a separate entry in an index."
With a 9 element list you just created 9 indexes. If you expand the box to get some more resolution such as the 13 box example, you will then have 13 indexes on that property alone. You can see where this is going. It gets compounded if you even 1 single other list element in your model. If you had another list element with just 2 records you would have a total of 20 indexes (18 for the 2 lists and then 2 for the basic indexing). This causes a number of issues. The two you pointed out, updating and data storage. Updating has to hit each and every index so updates would be a huge bottleneck if the model is updated often. The other issue is (and correct me if I'm wrong on this anyone with more experience) is that because lists are stored as separate entities Big Table has to do multiple queries to return your result set. A bit of testing would probably be a good idea to see what the speed is. If you have a small dataset, you definitely won't have an issue. Check out this: http://code.google.com/appengine/docs/datastore/queriesandindexes.html#Big_Entities_and_Exploding_Indexes --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~----------~----~----~----~------~----~------~--~---
