Bug report (mine)

[Aaron Turner <aturner@linuxkb.org>]

I was working on the search engine a lot tonight, trying to get it working
sanely again.  (didn't get much done on the kbmirrormanage.pl :(

Anyways, I found a bug with our implimentation for restricting searches

Let's say Joe does a search from 1.4 (applications) and does a search for
"named".  Well he shouldn't get any hits, but he does.  For 1.42.3.5.7

The problem has to do with my string matching on 1.4 which also matches
1.42.x.y.z  or 1.409.a.b.c or 1.4586.d.e.f

Get the picture?

The only way around this is if I tack on to the restrict string a "." so:

1.4 becomes 1.4.

Problem is if 1.4 is the end of a branch and you do a search, you'll never
get any hits, because the end of a branch doesn't have a .

So Jason, any chance we can add a . at the end of the op param?  Another
option that crossed my mind, is if you go to a cat/app that has no
children cats/apps we might just want to switch them to article listings
view.  Or I can have search.pm do a sql lookup to determine if there are
any children of the current cat and not add the . at the end in those
cases.  That is probably the least desireable because of the added memory
footprint for the DB connetions/modules.

I'm sure there are plenty of other options, but only a few decent.

Thoughts anyone?

--
Aaron Turner, Core Developer       http://vodka.linuxkb.org/~aturner/
Linux Knowledge Base Organization  http://www.linuxkb.org/
Because world domination requires quality open documentation.
aka: aturner@vicinity.com, aturner@pobox.com, ion_beam_head@ashtech.net
The difference between `Unstable' and `Usable' is only two characters: NT