Because building indexes takes more cpu time and datastore space, otherwise Google wouldn't offer "indexed=False" parameter for static properties.
BTW, how about an expando with several dynamic list properties? I think it can reach the index limit very soon. ---------- keakon 2010/2/27 Andrew Chilton <[email protected]>: > On 27 February 2010 13:58, 风笑雪 <[email protected]> wrote: >> Most time I only want the static properties of Expando to be indexed, >> but the dynamic properties are always automatically indexed too. >> >> Is there any way to remove these indexes, just like >> db.IntegerProperty(indexed=False) dose for the static properties? > > Unless you are hitting the index limit, why don't you want to index > these properties? > > Cheers, > Andy > > -- > contact: Andrew Chilton > website: http://www.chilts.org/blog/ > > -- > 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. > > -- 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.
