Objectify more-or-less passes data through to the low-level query API as-is. If you run .toString() on the Objectify query, you'll get some text that describes the query - it should be as useful as .toString() on the LL Query for the purposes of debugging (ie posting here).
Jeff On Tue, Aug 21, 2012 at 12:47 PM, Oleg Bashtenko <[email protected]> wrote: > No, I'm working with objectify-appengine. May it cause such problem? There > are only equality filters in my query, and one ordering field. Everything > works OK if I define such composite index on all fields used in the query, > but the point is to avoid that since there are too many possible > combinations of fields (user can select different search filters). > > -- > You received this message because you are subscribed to the Google Groups > "Google App Engine" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/google-appengine/-/sGmgOK0R9VoJ. > > 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.
