Bug#426366: postgresql-8.2: upper(), lower(), and ilike are broken on UNICODE databases

2007-07-08 Thread Emil Nowak
On 2007-07-06, at 21:34:52 Erwin Brandstetter wrote: Emil, are you sure you were connected to right database when running your tests? I have been having major problems with this bug in version pg 8.1.*, but I think it has been fixed in 8.2. Yes - it was the right database. See the

Bug#426366: postgresql-8.2: upper(), lower(), and ilike are broken on UNICODE databases

2007-07-08 Thread Erwin Brandstetter
Hi Emil! [EMAIL PROTECTED] wrote: Because your results were different I started to investigate problem on my postgres. Probably something was wrong main cluster. I made a backup of my databases, then removed postgress server with purge. Then I installed it once again, and recovered databases

Bug#426366: postgresql-8.2: upper(), lower(), and ilike are broken on UNICODE databases

2007-07-06 Thread Erwin Brandstetter
Hi Emil! Hi everyone! Emil, are you sure you were connected to right database when running your tests? I have been having major problems with this bug in version pg 8.1.*, but I think it has been fixed in 8.2. See the results of my tests: test=# select version();

Bug#426366: postgresql-8.2: upper(), lower(), and ilike are broken on UNICODE databases

2007-05-28 Thread Emil Nowak
Package: postgresql-8.2 Version: 8.2.4-1 Severity: normal When I try to use upper(), lower(), or ILIKE on UNICODE databases results are incorrect. For example: testy-utf=# select upper('Żółć'), lower('Żółć'); upper | lower ---+--- ūãłć | (1 row) And now the same thing on database