Geek Answers Handbook

Linq search french characters

I am usint EF and have a simple LINQ statement and want to search for words. So, there is a button for searching and sending a text field.

when the search contains "march" , which finds, for example. "des marchés" , but if I search for "marché" , he will not find. So this is a French symbol.

 listAgendaItems = dc.agenda.Where(a => a.libelle_activite.Contains(searchText) ).ToList<agenda>();

Agenda database and table have advanced properties -> Collation: French_CI_AS

So, how can I make sure that the French words? e.g. é, à, etc.

I also tried searching for "marche" , but did not find "marchés" .

+4
source share
2 answers

Your mapping to French_CI_AS is case insensitive, accent-sensitive. If you want the query for “marches” to match “marches,” you need French_CI_AI as a match. In most languages, this is NOT what native speakers want, because emphasis is semantically important, but it may depend on circumstances or context.

If, in fact, your users always want to search without emphasis, you should set this AI mapping property instead of AS to the table (or certain fields). Otherwise, if necessary, you can apply a table mapping in MS Sql for each query; keep in mind that if there is no index for this sorting, there can be a significant execution cost. This can be almost irrelevant if you make the request% wildcard%, however, since in any case you will have a full table scan in this case.

The last thing I checked was not able to directly specify the sort in the Linq query, so if you are case-insensitive on a one-time basis, you will need to use the direct-to-sql query through your data context.

Edited: Based on your comment, it looks like you are allowing HTML content to be stored in your database. You have numeric character references in your table that SQL Server knows nothing about, since they are characteristics of HTML, XML, and SGML. You can only do this for search if these characters are string literals in a suitable encoding.

NVARCHAR will save the contents in Unicode, in particular UTF-16, and VARCHAR will use Windows-1252 with a French mapping.

If you accept this input through web forms, make sure the page encoding is suitable. If you only support modern browsers (basically something IE5 +), UTF-8 is well supported, so you should consider using UTF-8 for all your requests and responses.

Make sure your web.config has something like this:

 <configuration> <system.web> <globalization requestEncoding="utf-8" responseEncoding="utf-8" /> </system.web> </configuration>

If you already have data stored with these numeric symbolic links in your database, you can delete them by translating & #ddddd; in the literal sequences of UTF-16, and save them again. Make sure you don't accidentally release semantically important NCRs, such as larger code pages or ampersands.

+3
source

this problem can be easily resolved with matching or full-text search . are you trying to move the search in the stored procedure and display that procedure with EF? Or, for the full text, you can create a query without using Linq expressions

 Context.ExecuteStoreQuery<Client> ("select * from TestDB.Clients as c where Freetext(c.description,{0}", searchText)

PS, if you get any result, please describe it.

0
source

More articles:


All Articles