From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
---|---|
To: | rees(at)ddcom(dot)co(dot)jp |
Cc: | pgsql-general(at)postgresql(dot)org, david(at)kineticode(dot)com |
Subject: | Re: UTF-8 and LIKE vs = |
Date: | 2004-08-24 06:13:54 |
Message-ID: | 20040824.151354.68036906.t-ishii@sra.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> > > 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).
--
Tatsuo Ishii
From | Date | Subject | |
---|---|---|---|
Next Message | Joel | 2004-08-24 06:38:26 | Re: UTF-8 and LIKE vs = |
Previous Message | Thomas Hallgren | 2004-08-24 05:29:34 | Re: Unsupported 3rd-party solutions (Was: Few questions |