[Xapian-discuss] Omega

[Jim Lynch]

I don't know if I figured out my problem or a way around it, but I've 
got something that works sort of.    Instead of using strings, I 
generated Xapian::Query objects and put them in the vector.  I used the 
query_parser method to generate the objects.

My next question is what is the significance of the "pos" parameters in 
the following output from get_description()

Xapian::Query(((toward:(pos=1) NEAR 11 posit:(pos=2)) OR less:(pos=3)))

When I do it programmatically I get pos=1 for all.  That didn't seem to 
make a difference in the results however I'd like to know what it means.

Thanks,
Jim.

Jim Lynch wrote:

> Thanks, now I want to extend omega to include variable proximity 
> searches and added the following at the beginning of the run_query 
> function:
>        vector<string> myTerms;
>        myTerms.push_back("less");
>        myTerms.push_back("february");
>        Xapian::Query nearMe(Xapian::Query::OP_NEAR,  
> myTerms.begin(),myTerms.end(),5);
>        query = Xapian::Query(Xapian::Query::OP_AND, query, nearMe);
>