Re: invalid UTF-8 byte sequence detected - Mailing list pgsql-general

From Michael Glaesemann
Subject Re: invalid UTF-8 byte sequence detected
Date
Msg-id 269F88E2-E97F-47CE-B232-E224F1350FCC@myrealbox.com
Whole thread Raw
In response to Re: invalid UTF-8 byte sequence detected  (mike <mike@thegodshalls.com>)
Responses Re: invalid UTF-8 byte sequence detected  (Wes <wespvp@syntegra.com>)
List pgsql-general
On Mar 16, 2006, at 14:42 , mike wrote:

> If you don't care to store those characters then maybe you should
> change
> the database character set to use SQL_ASCII instead of UTF-8.  I
> believe
> ASCII will quietly discard those characters when converting from
> UTF-8.

SQL_ASCII is *not* ASCII. See the "What's a good default encoding?"
thread on this same list from today.

http://archives.postgresql.org/pgsql-general/2006-03/msg00685.php

I don't believe it will discard anything on import if the database is
SQL_ASCII encoded.

Michael Glaesemann
grzm myrealbox com




pgsql-general by date:

Previous
From: Wes
Date:
Subject: Re: invalid UTF-8 byte sequence detected
Next
From: karly@kipshouse.org
Date:
Subject: Re: Indexes on array columns