From: | Harry Mantheakis <harry(at)mantheakis(dot)freeserve(dot)co(dot)uk> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Japanese words not distinguished |
Date: | 2005-07-12 21:05:52 |
Message-ID: | BEF9EF40.207BF%harry@mantheakis.freeserve.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>> Meanwhile, am I correct in assuming that re-initialising my database cluster
>> with "--locale=C" will solve the problem?
>
> AFAIK it should --- of course you won't get any very intelligent sorting
> or case folding, but at least it can tell the difference between
> different characters ;-). Be sure to still use encoding = unicode.
Okay, thanks for confirming that (!)
But... will setting the C locale affect how PostgreSQL sorts Latin-1 words?
If it does, I'm in trouble! I need to be able to sort (using ORDER BY
queries) English and other European names/words. (I've tried searching for
this topic, but failed to find an answer.)
Would specifying a locale for LC_COLLATE take care of this? Perhaps
something like this:
initdb --locale=C --lc-collate=en_GB.UTF-8 --encoding UNICODE
I'm sorry to drag this out. Perhaps I cannot have it both ways.
Kind regards
Harry Mantheakis
London, UK
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2005-07-12 21:09:11 | Re: Checkpoints are occurring too frequently... |
Previous Message | Joe | 2005-07-12 20:59:32 | Re: Converting MySQL tinyint to PostgreSQL |