Re: not valid character for Unicode

From: brian ally <brian(at)zijn-digital(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: not valid character for Unicode
Date: 2006-06-09 15:20:04
Message-ID: 448991A4.80002@zijn-digital.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Adam Witney wrote:
>
> Martijn van Oosterhout wrote:
>
>>On Fri, Jun 09, 2006 at 03:59:52PM +0100, Adam Witney wrote:
>>
>>>Hi,
>>>
>>>Im trying to upgrade from 7.4 -> 8.1 but it is failing with Unicode
>>>errors. The offending character is the greek character mu (often used
>>>for micro). Here is an offending string "BµG(at)S" (in case it doesn't
>>>appear in the email, the mu is between the B and the G)
>>>
>>>Any ideas why this character is not valid in Unicode?
>>
>>It's a valid unicode character, it's just you havn't encoded it in
>>unicode. It's probably in Latin-1. In that case, you need to specify it
>>in the client encoding...
>
>
> Hi Martijn,
>
> thanks for your quick response.
>
> Ok i am a bit confused by all this encoding stuff... i don't really know
> how to encode it in unicode? this is a text string that is extracted
> from a text file, i just put it in an INSERT statement.
>
> I have to replace fields with this in it with a valid string that will
> load into 8.1, do you know who i would do the conversion?
>

What did you use to extract it from the text file? If you're using some
text editor, ensure that it is set to UTF-8.

brian

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2006-06-09 15:20:46 Re: Fabian Pascal and RDBMS deficiencies in fully implementing the relational model
Previous Message Tom Lane 2006-06-09 15:18:23 Re: How to set the global OID counter? COPY WITH OIDS does