Tony, I think this should be determined by the server-side code. If we start adding too many options to jqGrid it is going to become too large and performance will become increasingly hard to tune from your end. I cannot see a situation where a user should decide whether or not a search option should be case sensitive or not, for example address, name, etc should always be case insensitive due to the nature of the Internet today, most folks texting today do not care about case. Anyway, doubleforte, not saying your request has no value but we need to always keep in mind we all use this GREAT plugin and want to keep it lean and mean

doubleforte, how much data are you trying to search through client-side; i.e. how many rows and how does the client-side search/filter affect performance of having to load all data? I'm just curious as I always hit the database for every request as a rule because it is hard to say how a list may grow in size over time and I'm not sure doing client-side filtering outweights the performance hit of loading all the data?

Any updates on case INsensitive search?

Anyone manage to

Hi Oleg,

This is exactly what I was looking for .

Hello!

The features described here are the part of jqGrid (since 3.8 version see here).

Regards
Oleg