| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
| Cc: | "Tatsuo Ishii" <t-ishii(at)sra(dot)co(dot)jp>, linux(at)alteeve(dot)com, 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:45:33 |
| Message-ID: | 8348.1115527533@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"John Hansen" <john(at)geeknet(dot)com(dot)au> writes:
> Tatsuo Ishii wrote:
>> We have developed patches which relaxes the character
>> validation so that PostgreSQL accepts invalid characters.
> That is just plain 100% wrong!!
That was my first reaction too. Why would this be a good idea?
If someone does want an encoding-agnostic database, they can
set it as SQL_ASCII.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2005-05-08 05:30:45 | Re: [HACKERS] Invalid unicode in COPY problem |
| Previous Message | John Hansen | 2005-05-08 04:29:08 | Re: [HACKERS] Invalid unicode in COPY problem |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2005-05-08 04:48:33 | Re: Patch for collation using ICU |
| Previous Message | John Hansen | 2005-05-08 04:29:08 | Re: [HACKERS] Invalid unicode in COPY problem |