I haven't tried that, but the indexes show that theyre built and serving. For some of the entities I didn't assign a TextProperty object, rather it was a string, and those are serving correctly. So it seems to be just the ones that are still db.Text that aren't being retrieved. Queries on a different property for the same entity returns all of them, but queries on the new StringProperty only return some.
On Oct 19, 2:06 pm, William Montgomery <[email protected]> wrote: > Have you tried vacuuming your indexes and updating them again, it could just > be that the index isn't in place to support the String queries yet? > > Will. > > 2009/10/19 tamakun <[email protected]> > > > > > > > Can anyone tell me if they've run into a similar problem to the > > following? > > > I had an entity with a TextProperty originally, i wanted to add a > > StringProperty so I updated the model and added new indexes for > > querying based on the new StringProperty. > > > It seems that assigning a StringProperty property with a TextProperty > > property will change the type of that property to db.Text so that it > > doesn't show up in queries/filters because those aren't indexable, but > > there doesn't seem to be a way to change it back. I've tried > > assigning None and doing put() on these entities but getting the same > > result (don't show up in queries that filter based on the new > > StringProperty). --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
