Re: [Tracker] wildcard search incomplete?

[Tshepang Lekhonkhobe <tshepang gmail com>]

2009/10/5 JÃrg Billeter <j bitron ch>:
> On Mon, 2009-10-05 at 10:57 +0100, Martyn Russell wrote:
> > On 05/10/09 08:17, Tshepang Lekhonkhobe wrote:
> > > Hi,
> > >
> > > I see wildcard (*) only cares if missing chars are after search string
> > > and not before. That means in aaabbbccc, if I did *bbb* and *ccc
> > > there'll be no results. At least that's according to
> > > tracker-search{,-tool}. Is it a simple fix or am I missing something?
> >
> > Prefix matching is only implemented at this point, we can implement
> > suffix matching too, but I am not sure if/when that will be. There are
> > certain speed issues with that AFAIK.
> >
> > JÃrg, any comment to add here?
>
> Suffix matching would be possible to implement but it would require an
> additional index. I don't think it's worth adding it, though, suffix
> matching doesn't sound like a primary use case.

Am now thinking of long filenames, and even long words. If one
searches for 'tracker', 'does-tracker-rock-hard.txt' won't be found,
and that'll raise eye-brows. That's a common use-case I think, and
AFAIR a number of ppl have asked such functionality in this list
already.

> It's not planned at the moment to implement the more interesting infix
> search *bbb* as it would either require an additional large index or it
> would be slow, unless there is a magic solution I'm not aware of ;)

How about making it available as an extra option, with a warning that
'it eats memory, disk, and CPU'. That is if it's easy to implement of
course.


-- 
my place on the web:
floss-and-misc.blogspot.com