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 4805A9FB27B for ; Fri, 11 Aug 2006 01:36:03 -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 12038-06 for ; Fri, 11 Aug 2006 04:36:02 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from grzm.com (grzm.com [200.46.204.98]) by postgresql.org (Postfix) with ESMTP id 875FD9FB271 for ; Fri, 11 Aug 2006 01:36:02 -0300 (ADT) Received: from localhost (unknown [200.46.204.128]) by grzm.com (Postfix) with ESMTP id 85923127D3A0 for ; Fri, 11 Aug 2006 05:36:01 +0100 (BST) Received: from grzm.com ([200.46.204.98]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 49284-09; Fri, 11 Aug 2006 04:35:55 +0000 (UTC) Received: from [172.16.1.101] (unknown [61.197.227.146]) by grzm.com (Postfix) with ESMTP id D760F127C4EB; Fri, 11 Aug 2006 05:35:52 +0100 (BST) In-Reply-To: <200608110307.k7B37AA22420@momjian.us> References: <200608110307.k7B37AA22420@momjian.us> Mime-Version: 1.0 (Apple Message framework v752.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <6C7F4101-7D91-480A-8540-7185174290B3@seespotcode.net> Cc: Gavin Sherry , Peter Eisentraut , pgsql-docs@postgresql.org, Tom Lane , Joe Conway Content-Transfer-Encoding: 7bit From: Michael Glaesemann Subject: Re: Values list-of-targetlists patch for comments (was Re: Date: Fri, 11 Aug 2006 13:35:46 +0900 To: Bruce Momjian X-Mailer: Apple Mail (2.752.2) X-Virus-Scanned: Maia Mailguard 1.0.1 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/32 X-Sequence-Number: 3650 On Aug 11, 2006, at 12:07 , Bruce Momjian wrote: > 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. Perhaps it may be confusing, but at the same time, it's educational to put VALUES at the top level. Having not read the SQL spec in detail, I do rely on the Postgres documentation as a quick reference. Thanks to the high-level of SQL-spec compliance, the Postgres documentation is pretty helpful in that way. And I'm always pleasantly surprised when I learn something new just from looking indices such as this. Michael Glaesemann grzm seespotcode net