Re: Add ENCODING option to COPY

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: Add ENCODING option to COPY
Дата
Msg-id 1297179761.24949.2.camel@fsopti579.F-Secure.com
обсуждение исходный текст
Ответ на Re: Add ENCODING option to COPY  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Add ENCODING option to COPY  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
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).

It probably shouldn't be changed inconsistently as part of an unrelated
patch, but I think the idea has merit.



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

Предыдущее
От: Dan Ports
Дата:
Сообщение: Re: SSI patch version 14
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: Re: patch: fix performance problems with repated decomprimation of varlena values in plpgsql