Re: Values list-of-targetlists patch for comments (was Re: - Mailing list pgsql-docs

From Bruce Momjian
Subject Re: Values list-of-targetlists patch for comments (was Re:
Date
Msg-id 200608110307.k7B37AA22420@momjian.us
Whole thread Raw
In response to Re: Values list-of-targetlists patch for comments (was Re:  (Gavin Sherry <swm@linuxworld.com.au>)
Responses Re: Values list-of-targetlists patch for comments (was Re:  (Michael Glaesemann <grzm@seespotcode.net>)
List pgsql-docs
Gavin Sherry wrote:
> > 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.

How many people are going to think of doing a VALUES(1)?  Isn't it just
like SELECT 1?  We can try making VALUES a non-toplevel command, and if
people get confused, we can promote in the documenation.  I think
starting it at top-level is perhaps confusing.

--
  Bruce Momjian   bruce@momjian.us
  EnterpriseDB    http://www.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

pgsql-docs by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: Values list-of-targetlists patch for comments (was Re: [PATCHES]
Next
From: Michael Glaesemann
Date:
Subject: Re: Values list-of-targetlists patch for comments (was Re: