I think that some transparency on this from the GAE team would be good. I would like to see in the control panel the size of each of the indexes that has been built -- including the single property indexes that are not shown. It would also be really nice to have a good way of marking a property in a model as 'not to be indexed'. If it is a string, then you can use a TextProperty type, but for all the other types, you are stuck with indexed properties. In fact, I don't really see why the process that autogenerates the index.yaml file shouldn't include the single property indexes as well.
It may be that the optimal strategy is to take all the properties that you don't want indexed and pickle them into blob on store, and unpickle them on a get. However, this just doesn't seem like the right approach.... This is an area where some tools are really called for -- to allow us to see where the datastore quota is actually being used. Philip On Mar 10, 12:30 pm, Jonathan Ultis <jonathan.ul...@gmail.com> wrote: > Or better, take your raw data size excluding BlobProperty and > TextProperty and multiply by 15x. I'm not sure what the multiplier is > on the unindexed properties yet. > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
