X-Original-To: pgsql-docs-postgresql.org@postgresql.org
Received: from localhost (wm.hub.org [200.46.204.128])
	by postgresql.org (Postfix) with ESMTP id 865829FB2E2
	for <pgsql-docs-postgresql.org@postgresql.org>;
	Thu,  3 Aug 2006 22:58:12 -0300 (ADT)
Received: from postgresql.org ([200.46.204.71])
	by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024)
	with ESMTP id 45516-02 for <pgsql-docs-postgresql.org@postgresql.org>;
	Fri,  4 Aug 2006 01:58:01 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-
Received: from linuxworld.com.au (unknown [203.34.46.50])
	by postgresql.org (Postfix) with ESMTP id C419F9FB2DD
	for <pgsql-docs@postgresql.org>; Thu,  3 Aug 2006 22:58:00 -0300 (ADT)
Received: from linuxworld.com.au (IDENT:swm@localhost.localdomain [127.0.0.1])
	by linuxworld.com.au (8.13.2/8.13.2) with ESMTP id k741vmUI017229;
	Fri, 4 Aug 2006 11:57:48 +1000
Received: from localhost (swm@localhost)
	by linuxworld.com.au (8.13.2/8.13.2/Submit) with ESMTP id
	k741vmQt017226; Fri, 4 Aug 2006 11:57:48 +1000
Date: Fri, 4 Aug 2006 11:57:48 +1000 (EST)
From: Gavin Sherry <swm@linuxworld.com.au>
To: Peter Eisentraut <peter_e@gmx.net>
cc: pgsql-docs@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>,
	Joe Conway <mail@joeconway.com>
Subject: Re: Values list-of-targetlists patch for comments (was Re:
In-Reply-To: <200608040321.48560.peter_e@gmx.net>
Message-ID: <Pine.LNX.4.58.0608041143430.17044@linuxworld.com.au>
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>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=
X-Spam-Level: 
X-Archive-Number: 200608/29
X-Sequence-Number: 3647

On Fri, 4 Aug 2006, Peter Eisentraut wrote:

> 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?

I asked this too. Tom pointed this out (I'd give the URL if I could find
it on archives):

--
You bet.  VALUES is parallel to SELECT in the SQL grammar, so AFAICS
it should be legal anywhere you can write SELECT.

The basic productions in the spec's grammar are respectively

         <query specification> ::=
              SELECT [ <set quantifier> ] <select list>
                <table expression>

and

         <table value constructor> ::=
              VALUES <row value expression list>
--

which seems to be the case from my reading of the spec.

Gavin