| From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
|---|---|
| To: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, <linux(at)alteeve(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Invalid unicode in COPY problem |
| Date: | 2005-05-08 04:15:16 |
| Message-ID: | 5066E5A966339E42AA04BA10BA706AE50A930C@rodrick.geeknet.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Tatsuo Ishii wrote:
> Sent: Sunday, May 08, 2005 12:01 PM
> To: linux(at)alteeve(dot)com
> Cc: pgsql-general(at)postgresql(dot)org; pgsql-hackers(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Madison Kelly | 2005-05-08 04:23:39 | Re: [HACKERS] Invalid unicode in COPY problem |
| Previous Message | Madison Kelly | 2005-05-08 04:02:37 | Re: Invalid unicode in COPY problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-05-08 04:22:01 | Re: rendezvous |
| Previous Message | John Hansen | 2005-05-08 04:07:29 | Re: Patch for collation using ICU |