Bug #602: Chinese characters query bug.
Young (young@my-feiqi.com) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Chinese characters query bug.
Long Description
db=> select objectid, name from state where countryOId=39 and name='xxx' order by name;
(Here xxx is a Chinese state word.)
Then I got the outputs:
objectid | name
----------+------
669 | xxx1
670 | xxx2
674 | xxx3
680 | xxx4
682 | xxx5
687 | xxx6
688 | xxx
...
(12 rows)
The names are all different in Chinese. You can see from
the results that the answers are not an unique one. The default
state choosed the first one. But actually it should be the one whicha's oid = 688.
Sample Code
No file was uploaded with this report
Not sure what version of PostgreSQL or what kind of platform you are
using, I would say this may be a bug with the locale database of your
OS. Try disable locale support of PostgreSQL.
--
Tatsuo Ishii
Show quoted text
Young (young@my-feiqi.com) reports a bug with a severity of 2
The lower the number the more severe it is.Short Description
Chinese characters query bug.Long Description
db=> select objectid, name from state where countryOId=39 and name='xxx' order by name;
(Here xxx is a Chinese state word.)Then I got the outputs:
objectid | name
----------+------
669 | xxx1
670 | xxx2
674 | xxx3
680 | xxx4
682 | xxx5
687 | xxx6
688 | xxx
...
(12 rows)
The names are all different in Chinese. You can see from
the results that the answers are not an unique one. The default
state choosed the first one. But actually it should be the one whicha's oid = 688.Sample Code
No file was uploaded with this report
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly
But we need to store multi-language informations.
We are using
7.1.3 under Mandrake Linux 8.1. We create database as:
Please tell us the PostgreSQL configuration option.
createdb -E MULE_INTERNAL somedb
I also tried this on the newest 7.2. It also worked like that.
Do you know Bluepoint linux 2.0( From China)? It also has
such problem with 7.1.3.
Do you need support for Chinese *and* ISO-8859-something at the same
time? If so, you need to turn off the local support. You are only
allowed *one* locale for a PostgreSQL installation, and if can't be
usefull for you anyway.
--
Tatsuo Ishii
Import Notes
Reply to msg id not found: 3C79B0EF.378D98A8@my-feiqi.com