History | Log In     View a printable version of the current page.  

jira.rhq-project.org has been archived and is now in read-only mode.

All issues have been moved to bugzilla.redhat.com. All new issues or updates to existing issues should be made through bugzilla.
Specific old RHQ issues can be found using a query of this form: https://bugzilla.redhat.com/show_bug.cgi?id=RHQ-1999.
New bugs can be raised here. Accounts at bugzilla.redhat.com have been created for existing RHQ users.
Open bugs raised in the last week can be found here.
Issue Details (XML | Word | Printable)

Key: RHQ-1613
Type: Sub-task Sub-task
Status: Accepted Accepted
Priority: Major Major
Assignee: Joseph Marques
Reporter: Charles Crouch
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
RHQ Project
RHQ-399

Add support for Comparison Type of "not equal"

Created: 19/Feb/09 10:33 AM   Updated: 28/Jul/09 07:00 PM
Component/s: None
Affects Version/s: 1.2
Fix Version/s: 1.4

Time Tracking:
Not Specified

Date of First Response: 19/Feb/09 11:13 AM


 Description  « Hide
Right now we have "=", "starts with", "ends with" and "contains", we should have "!=" too.

Arguably you could negate all of the conditions above, but "!=" was the one a customer asked for specifically.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Joseph Marques - 19/Feb/09 11:13 AM
charles, do you mean adding another substring function:

resource.name.notContains = "RHQ"

or do you want a new operator:

resource.name != "RHQ"

Charles Crouch - 19/Feb/09 04:29 PM
See case 268166 for more details.

Joseph Marques - 26/Feb/09 12:40 PM
to do this properly, i'd have to support the logical opposite of all operators today, which is startsWith, endsWith, contains, and ==