| From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Bruce Momjian" <bruce(at)momjian(dot)us>, "Itagaki Takahiro" <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: UTF8 with BOM support in psql |
| Date: | 2009-10-20 15:54:49 |
| Message-ID: | 4ADD96F9020000250002BB9B@gw.wicourts.gov |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
> What I think we might sensibly do is to eat the leading BOM of an
> SQL file iff the client encoding is UTF8, and otherwise treat it as
> just bytes in whatever the encoding is.
Only at the beginning of the file or stream? What happens when people
concatenate files? Would it make sense to treat BOM as whitespace in
UTF-8, or maybe ignore it entirely?
-Kevin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-10-20 16:00:59 | Re: Application name patch - v2 |
| Previous Message | Merlin Moncure | 2009-10-20 15:53:03 | Re: Controlling changes in plpgsql variable resolution |