From: | "Jrg Haustein" <joerg(dot)haustein(at)urz(dot)uni-hd(dot)de> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #1837: varchar/text operator "=" not unicode safe? |
Date: | 2005-08-19 15:08:38 |
Message-ID: | 20050819150838.21487F0E78@svr2.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged online:
Bug reference: 1837
Logged by: Jrg Haustein
Email address: joerg(dot)haustein(at)urz(dot)uni-hd(dot)de
PostgreSQL version: 8.0.3
Operating system: Linux (SuSE 9.1)
Description: varchar/text operator "=" not unicode safe?
Details:
I have a UNICODE database, trying to compare two unicode strings (Ethiopic
characters). Client encoding is also UNICODE:
testdb=> select ' '=' ';
?column?
----------
t
(1 row)
Clearly, it can be seen that they are not equal. The "LIKE" operator also
seems to think so:
testdb=> select ' ' LIKE ' ';
?column?
----------
f
(1 row)
What is the problem here?
The behavior is the same with SQL_ASCII databases and the SQL_ASCII client
encoding.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2005-08-19 15:10:45 | Re: BUG #1831: plperl gives error after reconnect. |
Previous Message | Stephan Szabo | 2005-08-19 15:03:39 | Re: [GENERAL] BUG #1830: Non-super-user must be able to copy |