| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
| Cc: | Jim Nasby <jim(at)nasby(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: psql blows up on BOM character sequence |
| Date: | 2014-03-23 16:39:23 |
| Message-ID: | DAE51FA3-A74A-482E-B617-81C542EB3628@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mar 23, 2014, at 8:03, Guillaume Lelarge <guillaume(at)lelarge(dot)info> wrote:
>
> Just a quick comment on this. Yes, pgAdmin always added a BOM in every
> SQL files it wrote.
From http://stackoverflow.com/questions/2223882/whats-different-between-utf-8-and-utf-8-without-bom:
According to the Unicode standard, the BOM for UTF-8 files is not recommended:
2.6 Encoding Schemes
... Use of a BOM is neither required nor recommended for UTF-8, but may be encountered in contexts where UTF-8 data is converted from other encoding forms that use a BOM or where the BOM is used as a UTF-8 signature. See the “Byte Order Mark” subsection in Section 16.8, Specials, for more information.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomas Vondra | 2014-03-23 18:10:18 | Re: jsonb and nested hstore |
| Previous Message | Tom Lane | 2014-03-23 15:49:37 | Re: Useless "Replica Identity: NOTHING" noise from psql \d |