On Thursday 06 April 2006 18:53, Yonik Seeley wrote: > On 4/6/06, mark harwood <[EMAIL PROTECTED]> wrote: > > Maybe we should have as a standard part of Query: > > > > //immediate child queries only > > Query [] getNestedQueries();
This is another way to deal with composed queries: http://svn.apache.org/viewcvs.cgi/lucene/java/trunk/contrib/surround/src/java/org/apache/lucene/queryParser/surround/query/ComposedQuery.java?rev=209183&view=log In surround, this is the superclass for all queries that have an operator and subqueries. > > It's still the case that you often need to know what type of query the > parent is. > For example, a BooleanQuery with mandatory, optional, and prohibited clauses. > Or, as Marvin brings up, phrase queries, etc. > > One may not want to worry about terms that don't match when constrants > are applied (like a phrase) to begin with, but you don't want to > implement it in such a way that makes it hard to add later. > > IMO, the query hierarchy should be fully self-describable... user code > should be able to walk it and re-create the exact same thing if > desired. There is a visitMatchingTerms method here: http://svn.apache.org/viewcvs.cgi/lucene/java/trunk/contrib/surround/src/java/org/apache/lucene/queryParser/surround/query/SimpleTerm.java?rev=209183&view=log This is the superclass for the term queries such as truncated terms. Regards, Paul Elschot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
