Re: UTF8 with BOM support in psql
| От | Magnus Hagander |
|---|---|
| Тема | Re: UTF8 with BOM support in psql |
| Дата | |
| Msg-id | 9837222c0910200902y4e0ad560o1c188e0f495f8b15@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: UTF8 with BOM support in psql (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
2009/10/20 Tom Lane <tgl@sss.pgh.pa.us>: > Andrew Dunstan <andrew@dunslane.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. +1. >> Should we also do the same for files passed via \copy? What about >> streams on stdin? What about files read from the backend via COPY? > > Not thrilled about doing this on stdin --- you have no good > justification for assuming that start of stdin corresponds to a file > boundary somewhere. COPY files, maybe. Yeah, that seems a lot more error-prone. -- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
В списке pgsql-hackers по дате отправления: