There will also be some performance gains, as indexes are updated synchronously when you save an entity. I don't think they're huge gains, but if you have to save multiple entities where multiple indexes have to be updated it won't hurt.
On Wed, Dec 30, 2009 at 9:21 AM, OvermindDL1 <[email protected]> wrote: > On Wed, Dec 30, 2009 at 10:12 AM, Dennis <[email protected]> wrote: > > I'm thinking I should use “indexed=False” aggressively to reduce the > > datastore storage expansion. > > Seems like if I'm too aggressive with it, I can always add an index > > back and rebuild the index. > > Just want to see if others are also using this strategy. > > That is exactly what I was doing, works well for me. > > -- > > 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. > > > -- Ikai Lan Developer Programs Engineer, Google App Engine -- 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.
