[google-appengine] Re: Too many indexed properties for entity

2009-05-12 Thread baytiger
TextProperty and BlobProperty are ALREADY not indexed. So it doesn't make any difference. The problem with the searchable model is that it makes a few extra rows in your database that contains among other things a list of all the words that appear in your TextProperty. This means that it runs

[google-appengine] Re: Too many indexed properties for entity

2009-05-12 Thread Ben
Ok, thank you for the response. I was just worried i was missing something obvious. My method of keeping only the title property as searchable model, and the rest of the fields as normal DB models does work fine, just didn't seem the most efficient way to do it. but it looks like that is the

[google-appengine] Re: Too many indexed properties for entity

2009-05-12 Thread Devel63
What you are doing SHOULD work. I use SearchableModel with many lines in a TextProperty, plus StringProperties, ListProperties, and others. I have 20+ indexes explicitly defined for this core class, and it all works quite well. I don't see anything wrong in your class declaration below (other

[google-appengine] Re: Too many indexed properties for entity

2009-05-11 Thread Ben
I thought maybe the 1.2.2 update with the addition of indexed=false would solve this problem for me, but it doesn't seem to have any effect. I can move the title into a separate property is i mentioned above and that works ok, but i feel like i must be missing some other obvious solution here.

[google-appengine] Re: Too many indexed properties for entity

2009-05-08 Thread Devel63
You should be able to have a searchable TextProperty and a StringProperty. I do. If the advice below doesn't help, try posting your class definition here. On May 7, 10:27 am, ryan ryanb+appeng...@google.com wrote: http://code.google.com/appengine/docs/python/datastore/queriesandinde...

[google-appengine] Re: Too many indexed properties for entity

2009-05-08 Thread Ben
I didn't figure out what was causing the problem, but i solved it by moving my Title string prop to a separate searchable class with a reference property, and leaving the description in a standard db model. might not work for everyone but solved my problem. thanks for the help. On May 8, 10:11 

[google-appengine] Re: Too many indexed properties for entity

2009-05-08 Thread 风笑雪
SDK 1.2.2 can use indexed=False parameter on property constructor now. 2009/5/9 Ben bhym...@gmail.com I didn't figure out what was causing the problem, but i solved it by moving my Title string prop to a separate searchable class with a reference property, and leaving the description in a

[google-appengine] Re: Too many indexed properties for entity

2009-05-07 Thread djidjadji
If you put the description in a BlobProperty? Maybe that is not indexed by SearchableModel 2009/5/6 Ben bhym...@gmail.com: Hello, i have implemented a relatively basic app using app engine and so far most htings are working well.  however i am having some problems using