Closed
Bug 196101
Opened 23 years ago
Closed 23 years ago
group checks in sanitycheck should use ANSI-compliant SQL
Categories
(Bugzilla :: Administration, task)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: justdave, Assigned: justdave)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
2.16 KB,
patch
|
bbaetz
:
review+
|
Details | Diff | Splinter Review |
had to fix this for Sybase. :)
Patch coming
| Assignee | ||
Comment 1•23 years ago
|
||
| Assignee | ||
Updated•23 years ago
|
Attachment #116346 -
Flags: review?(bugreport)
| Assignee | ||
Comment 2•23 years ago
|
||
Note that the ordering of the column names in the comparisons is really what's
important here (the leftmost column needs to be on the left side of the = in the
join comparison), and not changing them to use INNER JOIN, but using INNER JOIN
makes it easier to read as long as we're screwing with it.
Comment 3•23 years ago
|
||
Comment on attachment 116346 [details] [diff] [review]
Patch
I'm OK with this.
However, what we really want, both here and in show_bug & friends, is to use a
MINUS query - ie:
<original query> where (assigned_to=<me> OR (param('useqacontact') and
qa_contact=<me>) OR reporter=<me> OR EXISTS (SELECT 1 FROM cc where
cc.bug_id=bugs.bug_id AND cc.who=<me>) OR NOT EXISTS (SELECT group_id FROM
bug_group_map WHERE bug_group_map.bug_id=bugs.bug_id MINUS SELECT group_id FROM
user_group_map WHERE userid=<me>)
Or something along those lines.
It would be worth timing, at least.
It also has the advantage that we can just have a sub for that extra clause,
withoth having to poke arround like we used to do, or hard code it like we
currently do.
Attachment #116346 -
Flags: review?(bugreport) → review+
| Assignee | ||
Updated•23 years ago
|
Flags: approval+
Target Milestone: --- → Bugzilla 2.18
| Assignee | ||
Comment 4•23 years ago
|
||
Checking in sanitycheck.cgi;
/cvsroot/mozilla/webtools/bugzilla/sanitycheck.cgi,v <-- sanitycheck.cgi
new revision: 1.64; previous revision: 1.63
done
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•