Rich Lane <rl...@club.cc.cmu.edu> writes: > Agreed that Xapian should have this, and I'll probably implement it. We > still need to support people using older Xapian versions though. Whether > this means a log message telling them to use explicit ANDs in their > query, or automatically transforming simple-enough queries into what we > think they actually want, I don't know. I'll also need to add a > workaround for the earlier Xapian bug before this index gets wider > usage.
I've now opened a Xapian ticket for this: http://trac.xapian.org/ticket/402 Patches are certainly most welcome, especially as I'm currently trying to focus on getting Xapian 1.2.0 out of the door. I don't see a satisfactory workaround for it, sadly. > As far as which index to make the default, Ferret has the advantage of > being installable as a gem dependency. I think this ease of installation > is important enough to block Xapian for now, unless someone can create a > Xapian gem. There's been interest in this before: > http://article.gmane.org/gmane.comp.search.xapian.devel/1408/ I recently noticed this gem version of (modified) xapian-bindings: http://groups.google.com/group/acts_as_xapian/msg/1bbb1e0d3753a0b7 I've not had a chance to look at it yet though, so I don't know if the changes mentioned are compatible or not. Assuming they're useful, they probably should be folded in upstream - more idiomatic wrappers are a desirable improvement (though if they're incompatible we'd need some sort of migration plan). It doesn't seem productive to have forked versions like this either. Cheers, Olly _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk
