Closed
Bug 175334
Opened 23 years ago
Closed 11 years ago
Make default owner search "begins with" rather than "is"
Categories
(Bugzilla :: Query/Bug List, enhancement, P3)
Bugzilla
Query/Bug List
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: selmer, Unassigned)
Details
A change is coming that will make bug owner searches default to exact matches.
Most names are unique without the @foo.bar portion, so changing the default to
"begins with" might alleviate performance problems without reducing the
convenience of the "contains" default.
This recommendation is only viable if the performance of "begins with" is near
that of "is" or at least sufficiently better than "contains" to be acceptable.
All the while that I used the default "contains" setting, I really meant "begins
with" anyway. This might allow most people to switch to the new setup without
even knowing that anything had changed.
Comment 1•23 years ago
|
||
bbaetz: could this be done using a ^Foo regexp? And would it perform on a par
with exact match, or much worse?
Gerv
Comment 2•23 years ago
|
||
We'd want to use |LIKE foo%|, which is probably more efficent. Also, since the
start of the string is fixed, the db can use an index to do the lookup.
Updated•23 years ago
|
Priority: -- → P3
Target Milestone: --- → Bugzilla 2.20
Updated•22 years ago
|
OS: Windows 2000 → All
Hardware: PC → All
Updated•22 years ago
|
Assignee: endico → nobody
Comment 4•21 years ago
|
||
Bugzilla 2.20 feature set is now frozen as of 15 Sept 2004. Anything flagged
enhancement that hasn't already landed is being pushed out. If this bug is
otherwise ready to land, we'll handle it on a case-by-case basis, please set the
blocking2.20 flag to '?' if you think it qualifies.
Target Milestone: Bugzilla 2.20 → Bugzilla 2.22
Assignee: nobody → query-and-buglist
QA Contact: mattyt-bugzilla → default-qa
Target Milestone: Bugzilla 2.22 → ---
Comment 5•16 years ago
|
||
What do you mean by "default owner"? Which page, which field??
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•