Re: Documentation patch: change a name in a grammar rule

Поиск
Список
Период
Сортировка
От Nicolas Barbier
Тема Re: Documentation patch: change a name in a grammar rule
Дата
Msg-id b0f3f5a10604151421j1e24def1m3560ef35bb0fa229@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Documentation patch: change a name in a grammar rule  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: Documentation patch: change a name in a grammar rule  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-patches
2006/4/15, Tom Lane <tgl@sss.pgh.pa.us>:

> s/prominently/at all/ ... I don't think the proposed patch is an
> improvement, and in fact see nothing wrong with the use of "parameter"
> here.  If we want to abandon "parameter" as the official documentation
> term for GUC variables, then there are dozens or hundreds of changes
> to be made in config.sgml, to say nothing of other files.

In for example set.sgml, just "name" is used for the exact same
concept. I changed the patch so that "varname" is used, because "name"
was already in use by this specific grammar. Maybe the usage of "var"
makes it less clear indeed, for people that know that those things are
always referred to as "parameters" and never as "variables". But then,
leaving it as-is doesn't solve the apparently occuring confusion
between "parameter" the GUC and "parameter" the "parameter to the
statement", as we have had at least three people in #postgresql that
made that exact mistake.

Nicolas

--
Nicolas Barbier
http://www.gnu.org/philosophy/no-word-attachments.html

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: [PATCH] Reduce noise from tsort
Следующее
От: Dhanaraj M - Sun Microsystems
Дата:
Сообщение: Re: Patch for bug #2073 (Can't drop sequence when created