I want to believe that this "bug" (if it is a bug), should already be known by everyone. Especially if the user deals with languages that use accented letters, such as: á, ê; ü; ñ etc.
When searching, for example, for a part that has the description "AVIÃO", it is necessary to type "AVI * O" to be successful. That is, I need to replace all the letters accented with "*".
I wonder if it's the same or is there a bug in the SQL query assembly?
Wilson Roberto Vasques Nunes.
Banknote catalog referee for Brazil.
Not sure I understand your problem as "AIRPLANE" doesn't have accented letters. What does "AVI*O" stand for in your case?
Sapientiae plerumque stultitia est comes.
Si c'est un grand plaisir d'être reconnu par ses amis, c'est peut-être encore plus flatteur d'être reconnu par ses adversaires.
Be yourself; everyone else is already taken.
Search works normally for words that contain non-basic Latin alphabet symbols, e.g. pelėda, Vydūnas, žemaitukas. So the problem applies only to ã and perhaps other specific letters.
I discovered the misconception of my post. Actually fast search with graphical accent works perfectly. The problem is noted in the advanced search. By filling in the "lettering" field with accented words, the search returns no result. To obtain the expected result, it is necessary to use wildcards (*).
Look ...
Wilson Roberto Vasques Nunes.
Banknote catalog referee for Brazil.