Ah, and there it is documented in the Query docs. However, it would be very handy if this threw an exception rather than returning null. Unfortunately, passing in a null Cursor in the fetch options works just fine - so what happens is that rather than getting an exception with an explanation of what you are doing wrong, the next query just continues from the beginning and you get a loop. Oops.
Thanks, Jeff On Mon, Dec 12, 2011 at 2:16 PM, Jason Collins <[email protected]> wrote: > IN (and NOT_EQUALS) result in MultiQuery which doesn't support cursors > as far as I know. > j > > On Dec 11, 7:21 pm, Jeff Schnitzer <[email protected]> wrote: >> Are there some kinds of queries for which cursors cannot be generated? >> >> I'm on Java SDK 1.6.0, using the "advanced queries" that let us escape >> exploding indexes. Whenever I request a Cursor, I get back null from >> the low level QueryResultIterator. When I click through to the GAE >> SDK source code it looks like the query class is some sort of >> "UncompileableQuery" which always returns null from getCursor(). Is >> this expected? Will it change in the future? >> >> FWIW, my query is this: >> >> Query<Club> query = ofy.load().type(Club.class) >> .filter("cells in", cells) >> .order(HasWords.SORT_FIELD) >> .limit(CLUBS_BATCH_SIZE); >> >> (cells is a geocells multi-property) >> >> Thanks, >> Jeff > > -- > 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. > -- We are the 20% -- 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.
