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

[Peter Eisentraut]

Tom Lane wrote:
> 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?"

The "top-level" SELECT for interactive use is

 ::=  

 ::=  | ...

 ::=  | ...

But this actually does resolve as just VALUES (something), so nevermind.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/

---(end of broadcast)---
TIP 6: explain analyze is your friend

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

[Simon Riggs]

On Thu, 2006-08-03 at 10:58 -0400, Tom Lane wrote:
> Gavin Sherry <[EMAIL PROTECTED]> writes:
> > Docs and regression tests attached.
> 
> I've applied the regression tests (with a few additions), but I'm
> feeling dissatisfied with this approach to documenting VALUES.
> It seems to be mostly missing the point about VALUES being usable
> whereever SELECT is.  I'm not at all sure what I'd do instead though.
> Should we give VALUES its own reference page?  That doesn't quite
> seem helpful either.  cc'ing to pgsql-docs for ideas.

The DB2 manual does exactly that and is not any clearer as a result,
even if it is fully normalised.

If we did that we'd need to emphasise that VALUES is more of a clause
than a new command.

-- 
  Simon Riggs
  EnterpriseDB  http://www.enterprisedb.com


---(end of broadcast)---
TIP 4: Have you searched our list archives?

   http://archives.postgresql.org