search for: op_wildcard

first, thank you,xapian! then I'd like to ask if it is possible to do a range query on terms(like the range query on values), or if it is just a wildcard(right truncation) match. the case is searching ip address bettween ?10.10.0.0? and ?10.10.255.255? the user want : 1. query "10.10.10.10" < ip < "10.10.10.12" gives "10.10.10.11" 2. query

Hi, I'm exploring using Xapian to to replace a database-backed people lookup. It's working well but I'd like to know if there's anything more I can do to increase accuracy. It handles partial phrases well, so long as the first part is complete (e.g. "Peter Bow" expands well). If instead I type "P Bow" it fails to work, as the expansion is done at the end. Is

...t the "isbn:" prefix would map to. But yes, that's the sort of pattern you'd have to use. One wrinkle with this is that (assuming you use the Xapian::TermGenerator class) "-" is a word separator character at index time - i.e. you'll get terms from 1-234-56789-0 and OP_WILDCARD only matches within a term. So you need different word splitting behaviour for this to work, which currently means you'll need to do it yourself instead of using TermGenerator as that isn't currently configurable. > 1 Could you mention how one enables and can take advantage of your &gt...

To Olly Betts: Thank you very much for any feedback. I apologise for this belated reply and also for the fact that the text of the previous posting appeared fragmented, due to its fixed chars/line format. With reference to: > Can, or could, one construct a query so that Omega (Xapian) can handle > this ? > > ... perhaps with some type of Regex ? > > It would seem

...like Xapian::Query("Peter Bow*") that will try to search for the single literal term `Peter Bow*`, which indeed wouldn't match anything in most databases. If you really wanted to wildcard expand all words in a query string, you'd have to parse it yourself, turn each word into an OP_WILDCARD query and combine those. I'd think that's likely to create a lot of false matches though, and wildcards are relatively expensive so you might want to limit how many words get wildcarded in a single query to avoid problems. > Also sometimes (though not always) substring matches would he...

...check for every >candidate document. > >But if you only actually have a small number of IP addresses and really >want to use terms, you can just iterate allterms from the Database >object and build an OP_SYNONYM query from all the matching terms. In >1.2.x, that's exactly how OP_WILDCARD is implemented (in master >OP_WILDCARD expansion is delayed until we process the Query tree, which >means we can avoid creating Query objects for every term in the >wildcard). > >Cheers, > Olly