Re: Unicode + LC_COLLATE - Mailing list pgsql-general

From Priem, Alexander
Subject Re: Unicode + LC_COLLATE
Date
Msg-id 2A07EC2D0BC2774AAD6F74769F60D52A08330B@ahmose.cict_ad.nl
Whole thread Raw
In response to Unicode + LC_COLLATE  ("John Sidney-Woollett" <johnsw@wardbrook.com>)
Responses Re: Unicode + LC_COLLATE
Re: Unicode + LC_COLLATE
List pgsql-general
> C locale basically means "sort by the byte sequence values".  It'll do
> something self-consistent, but maybe not what you'd like for UTF8
> characters.
>
> Does that sort rationally at all?  I should think you'd need to specify
> an LC_COLLATE setting that's designed for UTF8 encoding, not 8859-15.
>
> If you only ever store characters that are in 7-bit ASCII then none of
> this will affect you, and you can get away with broken combinations of
> encoding and locale.  But if you'd like to sort characters outside the
> minimal ASCII set then you need to get it right ...

But if you use anything other than C, you can't use indexes in Like-clauses,
right?

Would lc-collate=C be bad in combination with UNICODE encoding? What
lc-collate setting would you recommend for UNICODE encoding which will
provide good sorting for all (most) common languages? (dutch, english,
french, german)

Alexander Priem

pgsql-general by date:

Previous
From: Jeff Boes
Date:
Subject: Re: Looking for help building 'rhdb-explain' Visual Explain tool
Next
From: Michael Chaney
Date:
Subject: Re: FW: Postgres alongside MS SQL Server