Comment 10 for bug 607960

Stuart - yes, I was on staging -the %foo% times are consistent with production there.

I think the *intent* of the wildcard search is 'find all bugs from packages with similar package names' ? The fulltext search won't (intrinsically) find libbluray when someone searches for bluray.

So, to compare options
One - just use the fti across all packages. Upside: fast. Downside: Won't return bugs in libbluray for searches in bluray.

Two - bring in a new index for %foo% handling. Upside: its faster. Downside: Needs a custom extension to pg built.

Three - drop targetnamecache and instead use fti on the bugtarget fti - sourcepackagemumble in this case - which has the package descriptions and thus should find libbluray for a search on bluray.

Four - stop including all bugs on packages with similar strings by default. Some related bugs to this:
 https://bugs.edge.launchpad.net/malone/+bug/76322 - wants a separate 'packagename' field
 https://bugs.edge.launchpad.net/malone/+bug/174394 - suggest narrower searches rather than all packages
 I was sure there was a bug about lp bug search being unsatisfying when a package name matches the query, but I can't find it trivially,

Anyhow, If I were hacking on this, I think I'd add a packagename field to the distro search (and a project name to the project group search) and drop the %foo% OR clause completely - I'd use the packagename/projectname field as an AND clause instead, when present, and when its not present search only on what the user put in.