Message-ID: <9054.125.24.219.40.1188488365.squirrel@webmail.xs4all.nl>
In-Reply-To: 
 <BF8B7E5C1F593446B8C0AD412C265ED7014BECAA@BANMLVEM04.e2k.ad.ge.com>
References: 
 <BF8B7E5C1F593446B8C0AD412C265ED7014BECAA@BANMLVEM04.e2k.ad.ge.com>
Date: Thu, 30 Aug 2007 22:39:25 +0700 (ICT)
Subject: Re: Problem with character encodings.
From: "Jeroen T. Vermeulen" <jtv@xs4all.nl>
To: "Korumilli, Bala S (GE Healthcare)" <Bala.Korumilli@ge.com>
Cc: pgsql-interfaces@postgresql.org
User-Agent: SquirrelMail/1.4.8
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit

On Thu, August 30, 2007 16:29, Korumilli, Bala S (GE Healthcare) wrote:

> I also tried inserting the character using its CODE. Characters 176, 186
> for  code page 1252. And character 248 for code page 437 .
> And I also tried all the characters from 128 to 255. For all these
> characters, Postgres is giving the same error.

So you also tried sending raw byte values for the UTF-8 character?  For
codepoint 176, I think that would be 0xc2 (194) followed by 0xb0 (176, by
pure coincidence).

If that failed as well then it sounds as if the database was not set up as
a Unicode one after all.  That's where it get system-specific and I
probably can't help you with it, but it sounds as if your database may
have been set up for ASCII.


> Can you please eloborate on this I could not understand this sentence.
> "The database doesn't expose its encoding IIRC, only its character set.
> So it's possible that that should be Unicode, not UTF-8."

It's only a small point, but IIRC the "encoding" given for a postgres
database set up to support Unicode is normally "Unicode," not "UTF-8."


Jeroen