Skip site navigation (1) Skip section navigation (2)

Re: UTF-8 and LIKE vs =

From: Joel <rees(at)ddcom(dot)co(dot)jp>
To: pgsql-general(at)postgresql(dot)org
Cc: david(at)kineticode(dot)com, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
Subject: Re: UTF-8 and LIKE vs =
Date: 2004-08-24 06:38:26
Message-ID: 20040824153204.1B9A.REES@ddcom.co.jp (view raw or flat)
Thread:
Lists: pgsql-general
Just want to check this --

> > > > The following should end up posted as shift-JIS, but
> > > >
> > > > テスト
> > > > and
> > > > てすと
> > > >
> > > > should collate the same under some contexts, since it's more-or-less
> > > > equivalent to a variation in case.
> > > 
> > > Do you mean if you search for
> > > 
> > >    SELECT * FROM keyword where name = 'テスト';
> > > 
> > > You might expect it to return a row with name set to 'てすと'?
> > 
> > If the locale machinery iw functioning correctly (and if I understand
> > correctly), there ought to be a setting that would allow those to
> > collate to the same point. 
> > 
> > I'm not sure what the settings would be, or if it's fully funtional yet.
> > Maybe Tatsuo would know? (Hope he doesn't mind me CC-ing him.)
> 
> I'm not sure what the point of the original question was, but I know 
> that
> 
> 	SELECT * FROM keyword where name = 'テスト';
> 
> should work if locale = C and encoding is either EUC_JP or UTF-8 on my
> standard Linux box (of course I did initdb --no-locale).

(query is katakana)

    SELECT * FROM keyword where name = 'テスト';


returns a record whose name field is 'てすと' (hiragana)?

Doesn't this require some LC_COLLATE flag?

(I suppose I should try this myself.)

-- 
Joel <rees(at)ddcom(dot)co(dot)jp>


In response to

Responses

pgsql-general by date

Next:From: Tatsuo IshiiDate: 2004-08-24 06:47:18
Subject: Re: UTF-8 and LIKE vs =
Previous:From: Tatsuo IshiiDate: 2004-08-24 06:13:54
Subject: Re: UTF-8 and LIKE vs =

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group