search does not work with polish signs

[acglj]

build 73: the result of search is empty when there is polish sign in the word, like ą, ę, ł, ń, ś, ż...
It definitely worked in previous builds :-(

Jacek

[UncleJohnsBand]

build 73: the result of search is empty when there is polish sign in the word, like ą, ę, ł, ń, ś, ż...
It definitely worked in previous builds :-(

Jacek

Do you mean if you enter a search phrase that contains these characters, the search results contain one of these characters or both?

[acglj]

I mean that if the search phrase contains one of those characters, the result list is empty. For example, for the word "wiadomości" there is no search result, but the emission starts every day at 19.30. And of course it exists in database -you can check at TVGuide window.
One more observation, done just now: no issue if you select "Case sensitive" and the phrase is "Wiadomości".

Jacek

[UncleJohnsBand]

I mean that if the search phrase contains one of those characters, the result list is empty. For example, for the word "wiadomości" there is no search result, but the emission starts every day at 19.30. And of course it exists in database -you can check at TVGuide window.
One more observation, done just now: no issue if you select "Case sensitive" and the phrase is "Wiadomości".

Jacek

If you do not select case sensitive then the phrase that you enter is converted to all uppers and the search looks at the programme's Title, Sub-Title, etc. with the upper command.

When you select case sensative the phrase is passed in as-is and is compared against the programme's Title, Sub-Title, etc. as-is...

I am guessing something happens when the phrase is converted to upper.

I'll have to run it through the debugger and see what may change to see if I can fix the problem.

[acglj]

Thanks for quick action...

[UncleJohnsBand]

Thanks for quick action...

Can you do me a favor and try doing the search without the special character and see what happens.

Wiadomości

Looking at what is happening I am thinking this may be something in SQL Lite....the code correctly uppercases the search and retains the special character.....I thought perhaps it was loosing it.

Prior to release 73 the search was searching against actual programme objects....which was basically a string to string compare.

With build 73 search performance was greatly enhanced by searching against the database data directly. To avoid having to do an exact match the search string is made all upper case and the query against the database is using the database command of UPPER when doing the search.....I am thinking that the database query language may not be able to handle the special character when making the database info all uppercase.

Doing a search against Wiadomosci instead of Wiadomości will help test the therory....if it finds a match then that is what it is....if it doesn't then I am not sure what could be going on.

[acglj]

Unfortunately, no good result with "Wiadomosci" (neither with Case sensitive checked nor unchecked).
So, the only positive serch for "Wiadomości" with Case sensitive on.

Jacek