Opened 16 years ago
Last modified 16 years ago
#3173 new enhancement
Make query string transformation behave more to expectations
| Reported by: | stippi | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | Unscheduled |
| Component: | Applications/Tracker | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | olive@… | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
Users will have build up some experience doing web searches. Therefore, the default/initial mode for Tracker queries should transform the input string in a way that aligns with the expectations built up from using Google and other search engines. To give an example: I knew I must have a song somewhere which contains the words "Love" and "Communication". Command-F > "Love Communication", but the search didn't return anything. The query string is as follows: (name=="*[lL][oO][vV][eE] [cC][oO][mM][mM][uU][nN][iI][cC][aA][tT][iI][oO][nN]*")
It should have been this of course:
((name=="*[lL][oO][vV][eE]*")&&(name=="*[cC][oO][mM][mM][uU][nN][iI][cC][aA][tT][iI][oO][nN]*"))
And that even finds the song.
Also, as can be seen from the resulting query string, it's really expensive to make the query case insensitive. The FS query capabilities should be more targeted towards these real-world uses and have some in-built support for case-insensitive queries.
