I have the latest version of SQL Prompt (10.16.5.15563), but this issue has occurred on previous versions as well.
I would like the option to have Case Sensitivity turned off for SQL History. As an example, I search for three different casings of SharePoint and the results are different each time. All uppercase returns nothing, all lower case returns nothing, only when spelt with the exact casing do I get the result.
My expectation is that all three searches should return the same results, as I don't want casing to influence my search results. If not, this would mean I would have to remember the exact casing of objects, which hampers quickly finding objects.
Another example, search for the term OData. When I search for the term “ODATA” I only get 1 result, where it is the exact term, but this time casing is ignored. So this is different behaviour as to the above. I'm also expecting to see the result for where the table name contains ODATA with exact case matching, but this result does not show. Only once I type out more of table name (which I don't want to do because I don't remember the table name, hence why I'm searching for it) does it find the table name.
I have the latest version of SQL Prompt (10.16.5.15563), but this issue has occurred on previous versions as well.
I would like the option to have Case Sensitivity turned off for SQL History. As an example, I search for three different casings of SharePoint and the results are different each time. All uppercase returns nothing, all lower case returns nothing, only when spelt with the exact casing do I get the result.
My expectation is that all three searches should return the same results, as I don't want casing to influence my search results. If not, this would mean I would have to remember the exact casing of objects, which hampers quickly finding objects.
Another example, search for the term OData. When I search for the term “ODATA” I only get 1 result, where it is the exact term, but this time casing is ignored. So this is different behaviour as to the above. I'm also expecting to see the result for where the table name contains ODATA with exact case matching, but this result does not show. Only once I type out more of table name (which I don't want to do because I don't remember the table name, hence why I'm searching for it) does it find the table name.