Re: psql blows up on BOM character sequence

Поиск
Список
Период
Сортировка
От David E. Wheeler
Тема Re: psql blows up on BOM character sequence
Дата
Msg-id DAE51FA3-A74A-482E-B617-81C542EB3628@justatheory.com
обсуждение исходный текст
Ответ на Re: psql blows up on BOM character sequence  (Guillaume Lelarge <guillaume@lelarge.info>)
Ответы Re: psql blows up on BOM character sequence  (Tatsuo Ishii <ishii@postgresql.org>)
Список pgsql-hackers
On Mar 23, 2014, at 8:03, Guillaume Lelarge <guillaume@lelarge.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.

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: Useless "Replica Identity: NOTHING" noise from psql \d
Следующее
От: Tomas Vondra
Дата:
Сообщение: Re: jsonb and nested hstore