[google-appengine] Re: How to NOT index a field

2009-07-09 Thread dburns
I mean "vaguely recall", not "vaguely require", sorry. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe f

[google-appengine] Re: How to NOT index a field

2009-07-09 Thread Nick Johnson (Google)
Hi dburns, You can supply "indexed=False" to the constructor for b. You can also use a TextProperty, which is exactly equivalent to an unindexed StringProperty. -Nick Johnson On Thu, Jul 9, 2009 at 1:57 PM, dburns wrote: > > If I have something like: > >  class MyModel(db.Model): >    a = db.St

[google-appengine] Re: How to NOT index a field

2009-07-09 Thread dburns
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? That's interesting about StringProperty vs TextProperty. I'd assumed there was a different storage mechanism, but it sounds like the

[google-appengine] Re: How to NOT index a field

2009-07-09 Thread Nick Johnson (Google)
On Thu, Jul 9, 2009 at 2:15 PM, dburns 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

[google-appengine] Re: How to NOT index a field

2009-07-09 Thread dburns
Excellent. Many thanks. --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Google App Engine" group. To post to this group, send email to google-appengine@googlegroups.com To unsubscribe from this group, send email to