| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Hitoshi Harada <umi(dot)tanuki(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add ENCODING option to COPY |
| Date: | 2011-02-08 18:47:48 |
| Message-ID: | 1297190869.20104.1.camel@vanquo.pezone.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On tis, 2011-02-08 at 10:53 -0500, Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)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"?
The canonical name of that is UTF8. But you can quote it if you want to
spell it differently.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Noah Misch | 2011-02-08 18:49:48 | Re: SQL/MED - file_fdw |
| Previous Message | Peter Eisentraut | 2011-02-08 18:45:27 | Re: postponing some large patches to 9.2 |