One related thing. If you create a bunch of entities with indexes = True and later turn it to False. Those indexes still exist for existing entities, until you rewrite the records.
On Nov 20, 8:17 am, Kenneth <[email protected]> wrote: > I can certainly see forcing you to decide by not providing a default, that > makes you to think about it. Defaulting to off doesn't force you to do > anything, it just swings the balance to cost is more important than > functionality. I suspect you're going to be getting a lot of novices who > are wondering why their data isn't coming back, or worse who don't realise > their data isn't coming back. > > Actually, thinking about it some more, if you never create an index on a > property, ie as you said it start off at false, does that give you an > immediate error if you filter on that property? That would change my > opinion. -- 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.
