Comments
6 comments
-
Thanks for the feedback!
We've got both the wildcards and numbers issue logged. I think the main issue for me with the wildcards is how to implement them. SQL syntax (with the LIKE as you suggested) seems like a good idea given the fact it's a SQL tool. However alot of people are also familiar with the wildcards search engines use.
Is there a general preference from people? -
Robbie Thng wrote:Is there a general preference from people?
The only other one that I would find helpful would be one of regular expression sets of wildcards, but no one else in my group would find that helpful because they haven't used it and find it difficult to grasp. -
This is definitely something we would love more people to feedback on so maybe I'll check with our marketing department what the best way to go about that is.
Personally I do love regular expressions but I understand it's maybe not the most simple of search concepts. I think if we chose one it would either be the search engine based usage or the SQL ones.
If we add this in as a feature in the future I'll see if we can get some wider feedback on what is preferred. -
I think if regex can be an option (with a checkbox or other device to enable it) that would be great.
Don't think it should be the default however. -
+1 for the regex inclusion
-
Add another +1 here...
Add comment
Please sign in to leave a comment.
However, this tool is pretty much useless to me, if the search field does not have a "LIKE" option with the appropriate wild cards and if the tool ignores numbers, which it seems that it currently does.