On Thu, Jul 9, 2009 at 2:15 PM, dburns<[email protected]> wrote: > > Thanks Nick! > > Ah, I was convinced it had to be in index.yaml. OK, that's easy. Do > you consider it good practise to do this, or is it naive to think it > will help?
It's absolutely best practice to only index what you need to. It will make a difference to both storage size and update latency - you may not notice it for a single property, but the more you do it, the more impact it'll have. The only caveat is that if you later need something indexed, you'll have to change the property, then iterate through your datastore and re-put all the entities. > > That's interesting about StringProperty vs TextProperty. I'd assumed > there was a different storage mechanism, but it sounds like the two > names are essentially there for convenience. This is partly historical - indexed=False is a recent innovation, so previously the only way to specify that something shouldn't be indexed was to use a TextProperty. The other difference is that a TextProperty has no limit on its size, while a StringProperty is limited to 500 bytes (again for indexing reasons). -Nick Johnson > > DB > > > > -- Nick Johnson, App Engine Developer Programs Engineer Google Ireland Ltd. :: Registered in Dublin, Ireland, Registration Number: 368047 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
