Thanks for the reply -- yes, creating the en_US.utf8 locale and using
that, fixed all of my problems.
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: 24 February 2005 17:11
To: Jatinder Sangha
Subject: Re: [GENERAL] Unicode support problem
"Jatinder Sangha" <js(at)coalitiondev(dot)com> writes:
> I've setup the postgres database as follows:
> initdb -E UNICODE
> createdb -E UNICODE
> I have tried setting locale/lc_ctype to C, POSIX, iso_8859_1, all
> kinds of things, and nothing seems to fix it.
You can't just pick random combinations of locale and database encoding.
Any given locale setting implies a character set encoding, and you have
to use that same encoding as the database encoding; at least if you want
encoding-dependent operations such as upper()/lower() to work. The
locale you want for Unicode (UTF8) may be named something like
"en_US.utf8". Try "locale -a" to get a list of supported locales.
regards, tom lane
pgsql-general by date
|Next:||From: Andreas 'ads' Scherbaum||Date: 2005-02-25 12:04:15|
|Subject: Re: Tracing of tables deleting - how?|
|Previous:||From: Alban Hertroys||Date: 2005-02-25 11:31:20|
|Subject: Re: Table UPDATE statement|