Re: Problem with langage encoding

From: "Ronald Vyhmeister" <rvyhmeister(at)gmail(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Problem with langage encoding
Date: 2008-11-26 15:10:04
Message-ID: 02ABBA1E9ED84798843F6DCBB7F6B762@peregrino
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> The problem is that the database is UTF8, and it won't let me use the
> convert_to function because it says that the characters don't exist...
What
> I need to do is to pull the UTF8 from the database, tell postgres that
it's
> 8859-1, and then convert it to WIN1251... How?

>If the DB is in UTF8, you ought to be able to issue

> set client_encoding to 'WIN1251'

>after connection, and the conversion happens automatically. See:

> http://www.postgresql.org/docs/8.3/static/multibyte.html#AEN27483

>HTH,

>Ray.

Wish it would work... when I do it, I get:

ERROR: character 0xc3bd of encoding "UTF8" has no equivalent in "WIN1251"
********** Error **********
ERROR: character 0xc3bd of encoding "UTF8" has no equivalent in "WIN1251"
SQL state: 22P05

The DB is storing it UTF8, but it is really 8859-1... I need to force PG to
think that it's 8859-1 in spite of what it thinks it may be...

Ron

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ivan Sergio Borgonovo 2008-11-26 15:17:40 Re: case when evaluating else condition anyway?
Previous Message Raymond O'Donnell 2008-11-26 15:06:51 Re: Problem with langage encoding