Re: Add ENCODING option to COPY
| От | Hitoshi Harada |
|---|---|
| Тема | Re: Add ENCODING option to COPY |
| Дата | |
| Msg-id | AANLkTikY4XHuxkd1g9MeaLv_yWOy0990W92q7gy6ufj+@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Add ENCODING option to COPY (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
2011/2/9 Tom Lane <tgl@sss.pgh.pa.us>: > Peter Eisentraut <peter_e@gmx.net> writes: >> On fre, 2011-02-04 at 10:47 -0500, Tom Lane wrote: >>> The reason that we use quotes in CREATE DATABASE is that encoding >>> names aren't assumed to be valid SQL identifiers. If this patch isn't >>> following the CREATE DATABASE precedent, it's the patch that's wrong, >>> not CREATE DATABASE. > >> Since encoding names are built-in and therefore well known, and the >> names have been aligned with the SQL standard names, which are >> identifiers, I don't think this argument is valid (anymore). > > What about "UTF-8"? Then, quote it? db1=# set client_encoding to utf-8; ERROR: syntax error at or near "-" Regards, -- Hitoshi Harada
В списке pgsql-hackers по дате отправления: