Here is more info: error appears only in case I mix equality &
inequality operator on same property. For example:

SELECT * FROM IndexRecord WHERE nss = 'don' AND nss >= '_do' AND nss <
'_dp'

gives the exception.

Strange, though, that via admin console this query does not show any
error. But resultset is empty even though it should bring results!

On Nov 13, 11:48 am, anatoliy <anatoliy.arteme...@gmail.com> wrote:
> I have an entity with indexed property "nss" which is a collection.
>
> Making query like (produced via Query.toString()):
>
> SELECT __key__ FROM IndexRecord WHERE nss = qwe AND nss = wer AND nss
> = ert AND nss = rty AND nss = tyu
>
> causes randomly (e.g. it works occasionally) exceptions "no matching
> index found.." with indexes:
> <datastore-index kind="IndexRecord" ancestor="false" source="manual">
>         <property name="nss" direction="asc"/>
>         <property name="nss" direction="asc"/>
>         <property name="nss" direction="asc"/>
> </datastore-index>
>
> <datastore-index kind="IndexRecord" ancestor="false" source="manual">
>         <property name="nss" direction="asc"/>
>         <property name="nss" direction="asc"/>
>         <property name="nss" direction="asc"/>
>         <property name="nss" direction="asc"/>
> </datastore-index>
>
> I expected that datastore is able to reuse same index for a property
> if multiple filters specified. SDK does not generate index
> declarations in the datastore-indexes-auto.xml file.
>
> Strange thing that running that query from console works ok:
>
> SELECT * FROM IndexRecord WHERE nss = 'qwe' AND nss = 'wer' AND nss =
> 'ert' AND nss = 'rty' AND nss = 'tyu' AND nss = 'tydu'

-- 
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-appeng...@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.

Reply via email to