Hi Joshua, MultiQuery is there to facilitate queries where a single user query requires multiple datastore-level queries. The most common examples are 'IN' and '!=' queries. The reason ext.search extends this is to support fulltext search in conjunction with other filters that require multiple datastore queries.
-Nick Johnson On Mon, May 11, 2009 at 6:20 AM, joshuacronemeyer <joshuacroneme...@gmail.com> wrote: > > I recently noticed the SearchableMultiQuery class has been added to > google.appengine.ext.search. When I first saw the class name I got > excited because I thought it might be a workaround for the exploding > index problem that SearchableModel has (ie. being able to run a n > keyword search required n indexes). > > Unfortunately it doesn't look like it. MultiQuery is a class in > datastore that SearchableMultiQuery is extending. It is described as > 'Class representing a query which requires multiple datastore > queries.' So this seems to solve some more general query problem and > isn't specific to SearchableModel. > > That said, if anyone can give a good explanation of what MultiQuery is > all about I'd appreciate it. > --~--~---------~--~----~------------~-------~--~----~ 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-appengine@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 -~----------~----~----~----~------~----~------~--~---
