Good idea.. maybe something like this :) Properties that Aren't Indexed
Property values that aren't indexed are not findable by queries. This includes properties that are marked as not indexed, as well as properties with values of the long text value type (Text) or the long binary value type (Blob). To declare that a property be stored as non-indexed using the Model class, provide the indexed argument to the property model constructor with the value False, as follows: class MyModel(db.Model): unindexed_string = db.StringProperty(indexed=False) A query with a filter or sort order on a property will never match an entity whose value for the property is a Text or Blob, or which was written with that property marked as not indexed. Properties with such values behave as if the property is not set with regard to query filters and sort orders. http://code.google.com/appengine/docs/python/datastore/queriesandindexes.html On Sat, Feb 20, 2010 at 2:37 PM, notcourage <[email protected]> wrote: > Apps often have properties which don't need indexing but the datastore > creates two rows in the single property index tables per property > value per entity--effectively the entity is stored three times. If the > API allowed a property to be excluded from indexing, this overhead > would be reduced. > > -- > 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]<google-appengine%[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.
