From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter_e@gmx.net>
Cc: Gavin Sherry <swm@linuxworld.com.au>
Cc: pgsql-docs@postgresql.org, Joe Conway <mail@joeconway.com>
Subject: Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]
Date: Thu, 03 Aug 2006 22:36:23 -0400
Message-ID: <860.1154658983@sss.pgh.pa.us> (raw)
In-Reply-To: <200608040321.48560.peter_e@gmx.net>
References: <44B69778.5050104@dunslane.net>
<200608031911.48010.peter_e@gmx.net>
<Pine.LNX.4.58.0608041042551.16622@linuxworld.com.au>
<200608040321.48560.peter_e@gmx.net>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, peter_e@gmx.net, swm@linuxworld.com.au, mail@joeconway.com
Subject: Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]
In-Reply-To: <860.1154658983@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox