Yes it is possible. At first, a deprecated (but similarly named) field was indexed. I have since deleted the index for this table, however, and regenerated it with the proper fields.
On Mon, May 3, 2010 at 2:10 PM, Ulrich <[email protected]> wrote: > On 05/03/2010 08:17 PM, Grant wrote: >> >> I've got a large number of records with just a few fields. The field >> I'm interested in is called wordStr, and is a non multi-line string >> property. When I do a simple query like: >> >> SELECT * from wordEntry WHERE wordStr = 'SomeString' >> >> I get 'no results'. >> >> The index in question is 'Serving', and I even went so far as to >> delete it and then rebuild it. >> >> If I manually view one of the records, and click 'save' without >> changing anything, it becomes query-able. >> > > Is it possible that the wordStr property was not indexed (indexed=False) at > the time you were adding these entities? > > -Ulrich >> >> Other fields in these records work as expected. >> >> Anyone had similar problems/know what could be happening? >> >> -Grant >> >> > > -- > 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. > > -- 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.
