Open Bug 814361 Opened 12 years ago Updated 12 years ago

Search by keywords like KeyMe returns results for KeyMe KeyMe- KeyMe+ KeyMewhatever

Categories

(Bugzilla :: Query/Bug List, defect)

4.2.1
defect
Not set
normal

Tracking

()

People

(Reporter: simon.gareste, Unassigned)

References

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.11 (KHTML, like Gecko) Ubuntu/12.04 Chromium/20.0.1132.47 Chrome/20.0.1132.47 Safari/536.11 Steps to reproduce: Searched for a specific Keyword, in Advanced search/Detailed Bug Information/Keywords : KeyMe mode : contains all of the words Actual results: Returned results for Keyword KeyMe, Keyword KeyMe-, Keyword KeyMe+ Expected results: Should have just returned results for KeyMe. For searches on "normal" words/searches, meaning words not in Bugzilla's list of Keywords, this behavior seems normal. But when searching for a Keyword (that identifies a "family" of bugs, of sorts), I don't think it should return all the Keywords starting like the one given. I think it should return the result of /^KeyMe$/, not /^KeyMe.*$/
The SQL query contains: AND bugs.bug_id IN (SELECT bug_id FROM keywords INNER JOIN keyworddefs ON keywords.keywordid = keyworddefs.id WHERE INSTR(keyworddefs.name, 'helpwanted') > 0 AND keyworddefs.name REGEXP '(^|[^[:alnum:]])helpwanted($|[^[:alnum:]])') I don't see why the WHERE part is not simply: WHERE keyworddefs.name ='helpwanted'
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is a regression due to bug 579568, affecting 4.2 and newer.
Depends on: 579568
Keywords: regression
(In reply to Frédéric Buclin from comment #1) > I don't see why the WHERE part is not simply: WHERE keyworddefs.name > ='helpwanted' Ah, I see that is has been implemented in a generic way in https://bugzilla.mozilla.org/attachment.cgi?id=458134&action=diff#Bugzilla/Search.pm_sec5. Also, keywords are no longer treated as special since 4.2, see the "patch for trunk" in bug 490322.
Depends on: 490322
You need to log in before you can comment on or make changes to this bug.