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>
Cc: Joe Conway <mail@joeconway.com>
Subject: Re: Values list-of-targetlists patch for comments (was Re:
Date: Fri, 4 Aug 2006 10:52:12 +1000 (EST)
Message-ID: <Pine.LNX.4.58.0608041042551.16622@linuxworld.com.au> (raw)
In-Reply-To: <200608031911.48010.peter_e@gmx.net>
References: <44B69778.5050104@dunslane.net>
<Pine.LNX.4.58.0608031523090.4590@linuxworld.com.au>
<18685.1154617090@sss.pgh.pa.us>
<200608031911.48010.peter_e@gmx.net>
On Thu, 3 Aug 2006, Peter Eisentraut wrote:
> Tom Lane wrote:
> > Should we give VALUES its own reference page? That doesn't quite
> > seem helpful either. cc'ing to pgsql-docs for ideas.
>
> This is probably the sort of thing that should be explained part II "The
> SQL Language". In particular, section 7.2 is about table expressions,
> which this is either a case of or related to.
Yes, good idea.
>
> A few examples on the command references pages to show how it can be
> useful are probably OK, but the big picture shoulbd be developed in
> chapter 7 or so.
What do we want to do about documenting:
regression=# values(1);
column1
---------
1
(1 row)
It seems to me that if this isn't in the command reference we'll see an
email every few months say 'is this an undocumented feature?'. We can
cover it easily in Part II, 7.2 but people wont look there. Then again, it
just doesn't seem right to put it in the command reference as a 'top
level' command.
Gavin
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: swm@linuxworld.com.au, peter_e@gmx.net, tgl@sss.pgh.pa.us, mail@joeconway.com
Subject: Re: Values list-of-targetlists patch for comments (was Re:
In-Reply-To: <Pine.LNX.4.58.0608041042551.16622@linuxworld.com.au>
* 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