From: | Harry Mantheakis <harry(at)mantheakis(dot)freeserve(dot)co(dot)uk> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Japanese words not distinguished |
Date: | 2005-07-12 15:56:41 |
Message-ID: | BEF9A6C9.2073B%harry@mantheakis.freeserve.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
I run PostgreSQL 7.4.6 on Linux with a JDBC client.
I initialised my database cluster with the following initdb command:
initdb --locale=en_GB.UTF-8 --encoding UNICODE
I have now discovered that my database cannot distinguish Japanese names or
words - it throws unique constraint errors on a composite primary key that
includes a VARCHAR field which stores the names or words.
My tests indicate that the database treats all Japanese names/words as
equal.
Having searched the forum archives, it seems to me that I should have
specified "--locale=C" as the locale setting when I initialised my database
cluster.
I am planning to re-initialise my database cluster using the following
command:
initdb --locale=C --encoding UNICODE
Then, after defining the relevant groups and users, I intend to call
pg_restore with reference to a "tar.gz" dump file of my data.
I wonder if someone might be kind enough to confirm that this is the right
approach to solving the problem.
Many thanks!
Harry Mantheakis
London, UK
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-07-12 16:26:03 | Re: index bloat |
Previous Message | Karl O. Pinc | 2005-07-12 15:49:04 | Re: Db and schema names in logged errors |