In Server Mode, the Grid utilizes filtering capabilities provided by ORM used as a data access layer. ORM translates an object query into an SQL query and loads filtered data from the database. Therefore, it depends on the database server settings whether or not filtering operations are case- or accent-insensitive.
Most of database servers provide options to configure the case and accent sensitivity globally or for specific tables. We suggest using this feature as the most convenient way to enable the case- and accent-insensitivity for filtering operations. Refer to the documentation of your SQL server for additional details. For your convenience, we have found corresponding articles in the documentation for several mainstream SQL servers:
MS SQL Server
Collation and Unicode Support
Selecting a SQL Server Collation
Oracle
Linguistic Sorting and Matching
MySQL
Character Sets and Collations in General
Server Character Set and Collation
PS: There is an undocumented flag that forces Server Mode collections to ignore character casing: DevExpress.Data.Helpers.ServerModeCore.DefaultForceCaseInsensitiveForAnySource. If you enable this option in the application entry point (the Program.cs file in WinForms or Global.asax file in Web applications), Server Mode collections will include the ToLower function in the filter expression. Note that if you are using indexes to improve performance, SQL server can ignore them in this mode. Use this approach only when there is no way to configure the database server.
Im' stuck with this issue. Is this workaround available for .Net Core web apps? And 18.2 version?
Thanks.
Hello,
I've created a separate ticket on your behalf (T718909: Is it possible to use a case-insensitive filter in .NET core applications). It has been placed in our processing queue and will be answered shortly.
Hi Uriah,
I have been using MSSQL and everything was working fine technically but due to cost factor I have been exploring PostgreSQL which seems to no cost solution for me and performance wise much better as well. But I am running in to few difficulties, one of which is the case-sensitivity.
In my web XAF app, when the user searches any text then it has to be case sensitive. I looked at this post of yours and found that there is a global setting for making the search case in-sensitive. I have applied this static property and set it to true in the Global.asax file but that doesn't seems to be working either. Could you please guide me on how to get rid of this case sensitivity for Postgres
protected void Application_Start(Object sender, EventArgs e) { DevExpress.Data.Helpers.ServerModeCore.DefaultForceCaseInsensitiveForAnySource = true; }Hi Farooq,
I've created a separate ticket on your behalf (T724378: Does DefaultForceCaseInsensitiveForAnySource option work with PostgreSQL and XAF?). It has been placed in our processing queue and will be answered shortly.
To avoid problems with searches, I recreated XAF search controller, the idea is to convert the values to compare to uppercase as well as the value from the column by using the function to upper on the server side.Here you can find an article about my experiences with the search controller in XAF https://www.jocheojeda.com/2018/12/01/xaf-filtercontroller-case-insensitive-search/ feel free to take and/or modify the code as you needed