Re: UTF-8 and LIKE vs =

Поиск
Список
Период
Сортировка
От Joel
Тема Re: UTF-8 and LIKE vs =
Дата
Msg-id 20040825104943.AA17.REES@ddcom.co.jp
обсуждение исходный текст
Ответ на Re: UTF-8 and LIKE vs =  (David Wheeler <david@kineticode.com>)
Ответы Re: UTF-8 and LIKE vs =  (Tatsuo Ishii <t-ishii@sra.co.jp>)
Re: UTF-8 and LIKE vs =  (David Wheeler <david@kineticode.com>)
Список pgsql-general
On Tue, 24 Aug 2004 David Wheeler wrote

> On Aug 23, 2004, at 10:25 PM, Joel wrote:
>
> > 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.
>
> Bleh. There must be some distinction between them. It sounds like
> querying for synonyms.

Sorry, I guess I wasn't clear. It's almost directly corollary to
ignoring case. (Almost, but not quite.) Kind of like querying with "TEST"
and getting records with "test".

> > 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.)
> >
> > So, what was the original language and text of the queries you started
> > this thread with?
>
> Korean, but the database I was using has data in 10 different languages
> in it, making any locale-specific collation useless.

Which means that the correct solution now is beyond the question of what
did the vendor think you would want. No way the vendor is going to be
willing to think you really want that, in spite of the number of people
who want precisely that. We don't yet have a mechanism that works for
general multiple language solutions.

At this point in time, "no locale" is probably close to best practice,
but it leaves you a lot of work.

--
Joel <rees@ddcom.co.jp>


В списке pgsql-general по дате отправления:

Предыдущее
От: Lawrence C
Дата:
Сообщение: Re: [ADMIN] Dump and Restore
Следующее
От: Christopher Browne
Дата:
Сообщение: Re: Unsupported 3rd-party solutions (Was: Few questions