Re: UTF-8 and LIKE vs =

[Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>]

> > 
> > Ð ÐÐÐ, 23.08.2004, Ð 23:04, David Wheeler ÐÐÑÐÑ:
> > > On Aug 23, 2004, at 1:58 PM, Ian Barwick wrote:
> > >
> > > > er, the characters in "name" don't seem to match the characters in the
> > > > query - 'êëë' vs. 'ëíì' - does that have any bearing?
> > >
> > > Yes, it means that = is doing the wrong thing!!
> > 
> > The collation rules of your (and my) locale say that these strings are
> > the same:
> > 
> > [markus(at)teetnang markus]$ cat > t
> > êëë
> > ëíì
> > [markus(at)teetnang markus]$ uniq t
> > êëë
> > [markus(at)teetnang markus]$
> 
> wild speculation in need of a Korean speaker, but:
> 
> ian(at)linux:~/tmp> cat j.txt
> ããã
> íêì
> ìêì
> ìëì
> êëë
> ëíì
> ããã
> ian(at)linux:~/tmp> uniq  j.txt
> ããã
> íêì
> ããã
> 
> All but the first and last lines are random Korean (Hangul)
> characters. Evidently our respective locales think all Hangul strings
> of the same length are identical, which is very probably not the
> case...

Locales for multibyte encodings are often broken on many platforms. I
see identical things with Japanese on Red Hat. This is one of the
reason why I tell Japanese PostgreSQL users not to enable locale while
initdb...
--
Tatsuo Ishii