I have the same results using low-level api for app engine queries :| So... this makes it very interesting, the way queries are executed on the datestore (using admin console UI or the App engine API)... It makes one wonder :)
On Sep 29, 9:56 am, Vaclav Bartacek <[email protected]> wrote: > In JDO you probably need to use the method "contains()" if testing > members of > collections.http://www.datanucleus.org/products/accessplatform_1_1/jdo/jdoql_meth... > > Vaclav > > On Sep 28, 4:20 pm, Ice13ill <[email protected]> wrote: > > > I executed a GQL query to test for some results in Datastore viewer: > > SELECT * FROM DbLaw where keyWordsList='leg' and keyWordsList='24' > > it worked OK. > > > The same query using JDO: > > Query text: SELECT FROM biz.ebas.server.DbTest WHERE > > keyWordsList=='leg' && keyWordsList=='24' > > > Threw this exception: > > "The built-in indices are not efficient enough for this query and your > > data. Please add a composite index for this query.. An index is > > missing but we are unable to tell you which one due to a bug in the > > App Engine SDK. If your query only contains equality filters you most > > likely need a composite index on all the properties referenced in > > those filters." > > > How can this be possible ??? Low-level speaking, aren't the same > > Queries ? the same datastores ? > > What is the problem ? -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
