Postgres Pro
Downloads
Home   >   mailing lists

Re: Support UTF-8 files with BOM in COPY FROM - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Support UTF-8 files with BOM in COPY FROM
Date
Msg-id CA+TgmobGLpx0gEzk_qDUddzpMxYxbG-xGWJQ79iZwXSHfcZcLA@mail.gmail.com
Whole thread Raw
In response to Re: Support UTF-8 files with BOM in COPY FROM  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Support UTF-8 files with BOM in COPY FROM
List pgsql-hackers
Tree view 
On Mon, Sep 26, 2011 at 1:28 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> The thing that makes me doubt that is this comment from Tatsuo Ishii:
>> TI> COPY explicitly specifies the encoding (to be UTF-8 in this case).  So
>> TI> I think we should not regard U+FEFF as "BOM" in COPY, rather we should
>> TI> regard U+FEFF as "ZERO WIDTH NO-BREAK SPACE".
>
> Yeah, that's a reasonable argument for rejecting the patch altogether.

Yeah, or for making the behavior optional.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Support UTF-8 files with BOM in COPY FROM
Next
From: Tom Lane
Date:
Subject: Re: Support UTF-8 files with BOM in COPY FROM