By Default the Grid filters for text columns only do the following comparisons; Equal, Contains, Starts, Ends (& Not's) We are missing: Greater Than, Less Than, GE & LE. Given the alphabet is ordered, it is reasonable & desirable to add these 4 comparisons to text as well as numeric & date columns. This empowers a filter like (Surname >= "L" AND Surname < "O") so we can find all customers with Names starting with L, M & N
Although executing number compare operators for string values based on alphabetical order might be applicable in some situations, in general these operators are meaningful for numbers only and can confuse users. That is the reason why we assume number operators should be strictly for numbers. Note that you can apply equivalent filter expressions to the grid data source's filter (http://docs.telerik.com/kendo-ui/api/javascript/data/datasource#configuration-filter.filters) directly to achieve the same result, for example: (Surname >= "L" AND Surname < "O") can be translated to (Surname StartsWith "L" AND StartsWith "M" AND StartsWith "L")
Thanks for these additional details, David. I'll forward them to our product team to be contemplated and updated the status of the thread.
Thanks for taking time to consider this user need. 1. Note: I gave an easy example. What would you advise an End-User to type into the filter if they wanted all surnames between "Neil" AND "O'Lachlan". 2. These types of comparisons are available in Excel, all the MS Office products, every database product & many of your competitors controls. Which highlights the user demand for this capability & that other vendors disagree with your position. Clearly you decide what features you will offer in this competitive market. As developers we can always code around it or use other alternatives. That said adding these extra filters for every string column will be tedious. Perhaps consider an option for those of use who feel the need to live on the edge. It is a very common user requirement. Eg: Next time you register at a conference, notice they often break the lines into alphabetical groups. eg: A- Le, Lf - Mac, Mac - Z. 3. Would you care to elaborate on "Confuse Users": I assume you are referring to some Unicode character sets. OR Case Sensitive comparisons? Perhaps I'm overlooking something really bad. So at present concern is avoiding frustrated users. I can educate confused users.