vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| The following bug has been logged online: Bug reference: 1837 Logged by: Jörg Haustein Email address: joerg.haustein@urz.uni-hd.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. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |
| Thread Tools | |
| Display Modes | |
|
|