Re: Add ENCODING option to COPY
Hitoshi Harada <umi.tanuki@gmail.com>
From: Hitoshi Harada <umi.tanuki@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Peter Eisentraut <peter_e@gmx.net>, Itagaki Takahiro <itagaki.takahiro@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2011-02-08T16:25:22Z
Lists: 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