Re: Bug #602: Chinese characters query bug. - Mailing list pgsql-bugs

From Tatsuo Ishii
Subject Re: Bug #602: Chinese characters query bug.
Date
Msg-id 20020225105425I.t-ishii@sra.co.jp
Whole thread Raw
In response to Bug #602: Chinese characters query bug.  (pgsql-bugs@postgresql.org)
List pgsql-bugs
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

> 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
>

pgsql-bugs by date:

Previous
From: pgsql-bugs@postgresql.org
Date:
Subject: Bug #602: Chinese characters query bug.
Next
From: missive@frontiernet.net (Lee Harr)
Date:
Subject: missing foreign key fails silently using COPY