Re: [GENERAL] Invalid unicode in COPY problem - Mailing list pgsql-hackers

From John Hansen
Subject Re: [GENERAL] Invalid unicode in COPY problem
Date
Msg-id 5066E5A966339E42AA04BA10BA706AE50A930C@rodrick.geeknet.com.au
Whole thread Raw
Responses Re: [GENERAL] Invalid unicode in COPY problem
Re: [GENERAL] Invalid unicode in COPY problem
Re: [GENERAL] Invalid unicode in COPY problem
List pgsql-hackers
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 12:01 PM
> To: linux@alteeve.com
> Cc: pgsql-general@postgresql.org; pgsql-hackers@postgresql.org
> Subject: Re: [HACKERS] [GENERAL] Invalid unicode in COPY problem
>
> We have developed patches which relaxes the character
> validation so that PostgreSQL accepts invalid characters. It
> works like this:

That is just plain 100% wrong!!
Under no circumstances should there be invalid data in a database.
And if you're trying to make a database of invalid data, then at
least encode it using a valid encoding.

In fact, I've proposed strengthening the validation routines for UTF-8.

... John

pgsql-hackers by date:

Previous
From: "John Hansen"
Date:
Subject: Re: Patch for collation using ICU
Next
From: Alvaro Herrera
Date:
Subject: Re: rendezvous