| From: | David Christensen <david(at)endpoint(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, 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 16:02:02 |
| Message-ID: | 94DDAFD4-9A1F-4F8D-8F82-9E632EE5964F@endpoint.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 20, 2009, at 10:51 AM, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
>> 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.
>
> That seems relatively non-risky.
Is that only when the default client encoding is set to UTF8
(PGCLIENTENCODING, whatever), or will it be coded to work with the
following:
$ PGCLIENTENCODING=...nonutf8...
$ psql -f <file>
Where <file> is:
<BOM>
...
SET CLIENT ENCODING 'utf8';
...
EOF
Regards,
David
--
David Christensen
End Point Corporation
david(at)endpoint(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Grittner | 2009-10-20 16:07:45 | Re: Application name patch - v2 |
| Previous Message | Magnus Hagander | 2009-10-20 16:02:01 | Re: UTF8 with BOM support in psql |