Reformatted excerpts from Rich Lane's message of 2009-09-10: > I thought it was, but it turns out that unless you explicitly add AND > operators Xapian will OR terms over the same field such that > "label:foo label:bar" gives you the union instead of the intersection.
Ok. I only ask because I'm considering how to present the Xapian index option in 0.9---the options are to not say anything about it, to force everyone to switch to it, or anywhere in between. > We could fix this by patching Xapian to make this behavior > configurable, or we could come up with an index-agnostic simple query > language that doesn't support boolean operators. The former sounds easier to me. Especially since it seems like this is something Xapian should have... -- William <wmorgan-...@masanjin.net> _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
