Bug 817653 - Bug in advanced Activity query
Summary: Bug in advanced Activity query
Keywords:
Status: CLOSED DUPLICATE of bug 813118
Alias: None
Product: Beaker
Classification: Retired
Component: web UI
Version: 0.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Raymond Mancy
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-04-30 18:37 UTC by Bill Peck
Modified: 2014-12-08 01:11 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-05-09 03:47:28 UTC
Embargoed:


Attachments (Terms of Use)

Description Bill Peck 2012-04-30 18:37:12 UTC
Description of problem:
The advanced Activity query lets you query against System/Name and Distro/Name but it never joins these together so you end up taking down the DB server.

Version-Release number of selected component (if applicable):
0.8.2

How reproducible:
Everytime

Steps to Reproduce:
1. Select Distro/Name from Advanced query
2. Add another search item
3. Select System/Name from Advanced query
4. Fill in any values for these two
5. Execute
  
Actual results:
DB will spin and churn and probably crash. :-)

Comment 1 Raymond Mancy 2012-05-04 00:58:33 UTC
I'm trying to figure out how searching for both of these things makes sense.

Normally our search bar works by having each subsequent condition having an AND operation to the previous condition, the resulting data of each condition being a subset of the data of the previous condition. However in this case the data that System/Name filters on is unrelated to the Distro/Name data.

Unless I'm missing something, perhaps this page should be removed as part of 813118

Comment 2 Bill Peck 2012-05-04 13:59:59 UTC
The user was trying to find activity for a system running distro.  You can see how the current search bar is confusing and would lead the user to think they could do that search.

Comment 3 Raymond Mancy 2012-05-09 03:47:28 UTC
This possibility has been removed in 813118

*** This bug has been marked as a duplicate of bug 813118 ***


Note You need to log in before you can comment on or make changes to this bug.