![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
PostgreSQL version: 8.0.3 Operating system: Windows XP SP2 When compare two UTF-8 encoded string that contains Chinese words, the result is always TRUE |
#3
| |||
| |||
|
|
On Sun, 19 Jun 2005, Tom Lane wrote: Sorry, but UTF-8 encoding doesn't work properly on Windows (yet). Use some other database encoding. Shouldn't we forbid its creation then? |
|
We see these complaints too often. |
#4
| |||
| |||
|
|
Kris Jurka <books (AT) ejurka (DOT) com> writes: On Sun, 19 Jun 2005, Tom Lane wrote: Sorry, but UTF-8 encoding doesn't work properly on Windows (yet). Use some other database encoding. Shouldn't we forbid its creation then? There was serious discussion of that before the 8.0 release, but we decided not to forbid it. Check the archives; I don't recall the reasoning at the moment. |
#5
| |||
| |||
|
|
=20 UTF8 encoding works with the C locale assuming you don't care=20 about ordering of the character set, e.g. Japanese. =20 |
#6
| |||
| |||
|
|
UTF8 encoding works with the C locale assuming you don't care about=20 ordering of the character set, e.g. Japanese. =20 =20 Has anyone with the ability to compile postgresql on windows=20 tested the ICU patch? |
![]() |
| Thread Tools | |
| Display Modes | |
| |