Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]
Дата
Msg-id 860.1154658983@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]  (Peter Eisentraut <peter_e@gmx.net>)
Ответы Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-docs
Peter Eisentraut <peter_e@gmx.net> writes:
> Gavin Sherry wrote:
>> What do we want to do about documenting:
>> regression=# values(1);

> Out of curiosity, according to what theory should that be allowed?

Wrong question.  SELECT (for the general case of multi-row results)
and VALUES are exactly parallel in the SQL grammar; the right question
is "according to what theory are you allowed to issue a general SELECT?"

AFAICT the SQL spec only envisions "SELECT ... INTO some-variables",
restricted to a single-row result (cf <select statement: single row>
production) as being something a client can issue directly.  Every more-
complex case is apparently supposed to be handled by one-row-at-a-time
fetches from a cursor.

If you can persuade the community that they don't want SELECT in its
current form, you might be able to persuade me that VALUES shouldn't
be allowed either.

            regards, tom lane

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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]
Следующее
От: Tom Lane
Дата:
Сообщение: Re: [PATCHES] Values list-of-targetlists patch for comments (was Re: