Bug 1035309 - Change the search query to be case-insensitive
Summary: Change the search query to be case-insensitive
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-webadmin
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.4.0
Assignee: Oved Ourfali
QA Contact: Jiri Belka
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-27 14:11 UTC by Oved Ourfali
Modified: 2014-03-31 12:30 UTC (History)
7 users (show)

Fixed In Version: ovirt-3.4.0-alpha1
Clone Of:
Environment:
Last Closed: 2014-03-31 12:30:51 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 21214 0 None None None Never

Internal Links: 828080

Description Oved Ourfali 2013-11-27 14:11:46 UTC 
Description of problem:
Today when writing a query in the search bar, the search is case-sensitive, which isn't very user-friendly, as usually users would prefer a case-insensitive search


How reproducible:
Always

Steps to Reproduce:
1. Search for something in the search bar

Actual results:
The search is case-sensitive

Expected results:
The search should be case-insensitive, providing better results
Comment 1 Sandro Bonazzola 2014-01-13 13:56:18 UTC 
oVirt 3.4.0 alpha has been released including the fix for this issue.
Comment 2 Jiri Belka 2014-01-23 09:04:21 UTC 
Is case insensitiveness only for value or even for object/property?
Comment 3 Oved Ourfali 2014-01-23 09:13:48 UTC 
Well, the purpose was to handle the values, but I saw that queries like:
Vms:NaMe = fedor*

also work, so looks like it also handles that.
(The fix I applied was to pass this flag to the engine side... didn't implement some new functionality in the engine, so that's why I wasn't sure about that).
Comment 4 Jiri Belka 2014-01-27 13:20:09 UTC 
ok, ovirt-engine-3.4.0-0.2.master.20140112020439.git9ad8529.el6.noarch

uSers : nAme = everyONE output is OK
Comment 5 Sandro Bonazzola 2014-03-31 12:30:51 UTC 
this is an automated message: moving to Closed CURRENT RELEASE since oVirt 3.4.0 has been released
Note You need to log in before you can comment on or make changes to this bug.