[google-appengine] Re: Too many indexed properties for entity
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 out of indexes and explodes and gives you the too many indexes error. There is no way around this. Its, unfortunately, a pitfall of the system. I think we can assume that Google is working on it. But nobody knows when it will be ready. It is likely that their database structure was not built for such large indexes. On May 12, 1:57 am, Ben bhym...@gmail.com wrote: 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. my property is set like so: - class Item(search.SearchableModel): title = db.StringProperty(required=True) category = db.IntegerProperty() product = db.IntegerProperty() priority = db.IntegerProperty() description = db.TextProperty(indexed=False) contributors = db.StringProperty() - any ideas? On May 9, 12:20 am, 风笑雪 kea...@gmail.com wrote: 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 standard db model. might not work for everyone but solved my problem. thanks for the help. On May 8, 10:11 am, Devel63 danstic...@gmail.com wrote: 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.comryanb%2bappeng...@google.com wrote: http://code.google.com/appengine/docs/python/datastore/queriesandinde. .. describes this error. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
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 way to go. thank you for the response! On May 12, 3:35 am, baytiger troels...@gmail.com wrote: 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 out of indexes and explodes and gives you the too many indexes error. There is no way around this. Its, unfortunately, a pitfall of the system. I think we can assume that Google is working on it. But nobody knows when it will be ready. It is likely that their database structure was not built for such large indexes. On May 12, 1:57 am, Ben bhym...@gmail.com wrote: 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. my property is set like so: - class Item(search.SearchableModel): title = db.StringProperty(required=True) category = db.IntegerProperty() product = db.IntegerProperty() priority = db.IntegerProperty() description = db.TextProperty(indexed=False) contributors = db.StringProperty() - any ideas? On May 9, 12:20 am, 风笑雪 kea...@gmail.com wrote: 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 standard db model. might not work for everyone but solved my problem. thanks for the help. On May 8, 10:11 am, Devel63 danstic...@gmail.com wrote: 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.comryanb%2bappeng...@google.com wrote: http://code.google.com/appengine/docs/python/datastore/queriesandinde. .. describes this error. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
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 than, perhaps, the setting indexed=false on the TextProperty ... I haven't tried that). Two possible ways to explore: - Pardon for asking, but are you positive the error message is about the Item class you defined? - What indexes do you have defined in index.yaml for Item? On May 12, 9:58 am, Ben bhym...@gmail.com wrote: 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 way to go. thank you for the response! On May 12, 3:35 am, baytiger troels...@gmail.com wrote: 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 out of indexes and explodes and gives you the too many indexes error. There is no way around this. Its, unfortunately, a pitfall of the system. I think we can assume that Google is working on it. But nobody knows when it will be ready. It is likely that their database structure was not built for such large indexes. On May 12, 1:57 am, Ben bhym...@gmail.com wrote: 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. my property is set like so: - class Item(search.SearchableModel): title = db.StringProperty(required=True) category = db.IntegerProperty() product = db.IntegerProperty() priority = db.IntegerProperty() description = db.TextProperty(indexed=False) contributors = db.StringProperty() - any ideas? On May 9, 12:20 am, 风笑雪 kea...@gmail.com wrote: 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 standard db model. might not work for everyone but solved my problem. thanks for the help. On May 8, 10:11 am, Devel63 danstic...@gmail.com wrote: 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.comryanb%2bappeng...@google.com wrote: http://code.google.com/appengine/docs/python/datastore/queriesandinde. .. describes this error. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
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. my property is set like so: - class Item(search.SearchableModel): title = db.StringProperty(required=True) category = db.IntegerProperty() product = db.IntegerProperty() priority = db.IntegerProperty() description = db.TextProperty(indexed=False) contributors = db.StringProperty() - any ideas? On May 9, 12:20 am, 风笑雪 kea...@gmail.com wrote: 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 standard db model. might not work for everyone but solved my problem. thanks for the help. On May 8, 10:11 am, Devel63 danstic...@gmail.com wrote: 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.comryanb%2bappeng...@google.com wrote: http://code.google.com/appengine/docs/python/datastore/queriesandinde. .. describes this error. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
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... describes this error. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
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 am, Devel63 danstic...@gmail.com wrote: 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... describes this error. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
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 standard db model. might not work for everyone but solved my problem. thanks for the help. On May 8, 10:11 am, Devel63 danstic...@gmail.com wrote: 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.comryanb%2bappeng...@google.com wrote: http://code.google.com/appengine/docs/python/datastore/queriesandinde. .. describes this error. --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
[google-appengine] Re: Too many indexed properties for entity
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 search.SearchableModel. I have an model that is a SearchableModel, in it i have defined several properties including Title and description. Title is a stringProperty and description is a textProperty. Now this seemed to work in the development environment, but when i deployed it i seem to get the Too many indexed properties for entity error when trying to save the item to the datastore if i have more than about a line of text in the description. I have not manually defined any indexes and am simply letting the development environment create them before deploying. I don't necessarily need to search the description, but i definitely need to search the title, anyone know what i am doing wrong or how i can accomplish this? --~--~-~--~~~---~--~~ 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 google-appengine+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en -~--~~~~--~~--~--~---
