X-Original-To: pgsql-docs-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id B98633A4413
	for <pgsql-docs-postgresql.org@localhost.postgresql.org>;
	Mon,  1 Nov 2004 05:21:26 +0000 (GMT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 97117-09
	for <pgsql-docs-postgresql.org@localhost.postgresql.org>;
	Mon,  1 Nov 2004 05:21:21 +0000 (GMT)
Received: from fetter.org (dsl092-188-065.sfo1.dsl.speakeasy.net
	[66.92.188.65])
	by svr1.postgresql.org (Postfix) with ESMTP id 218853A43DA
	for <pgsql-docs@postgresql.org>; Mon,  1 Nov 2004 05:21:20 +0000 (GMT)
Received: from fetter.org (localhost.localdomain [127.0.0.1])
	by fetter.org (8.12.11/8.12.10) with ESMTP id iA15LIwi009378;
	Sun, 31 Oct 2004 21:21:19 -0800
Received: (from shackle@localhost)
	by fetter.org (8.12.11/8.12.11/Submit) id iA15LIpl009377;
	Sun, 31 Oct 2004 21:21:18 -0800
Date: Sun, 31 Oct 2004 21:21:17 -0800
From: David Fetter <david@fetter.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Docs <pgsql-docs@postgresql.org>
Subject: Re: Array function
Message-ID: <20041101052117.GI13884@fetter.org>
References: <20041101003614.GG13884@fetter.org>
 <4282.1099280447@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="5G06lTa6Jq83wMTw"
Content-Disposition: inline
In-Reply-To: <4282.1099280447@sss.pgh.pa.us>
User-Agent: Mutt/1.4.2i
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200411/5
X-Sequence-Number: 2640


--5G06lTa6Jq83wMTw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Sun, Oct 31, 2004 at 10:40:47PM -0500, Tom Lane wrote:
> David Fetter <david@fetter.org> writes:
> > Here's a little addition to the array functions & operators section of
> > the manual.  It adds a function array() to the list.
> 
> The ARRAY() construct isn't really a function; it is a special
> syntax documented in Array Constructors,
> http://developer.postgresql.org/docs/postgres/sql-expressions.html#SQL-SYNTAX-ARRAY-CONSTRUCTORS
> 
> The addition you propose is misleading, because it would lead people
> to expect to find array() in the output of \df, for example.  It
> might be reasonable to put in some kind of "see also"
> cross-reference in the array functions section, but we shouldn't
> list array() as though it were just like every other function in the
> section.

Good point.

Please find attached a different diff :)

Cheers,
D
-- 
David Fetter david@fetter.org http://fetter.org/
phone: +1 510 893 6100   mobile: +1 415 235 3778

Remember to vote!

--5G06lTa6Jq83wMTw
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="array.diff"

Index: doc/src/sgml/func.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/func.sgml,v
retrieving revision 1.221
diff -u -r1.221 func.sgml
--- doc/src/sgml/func.sgml      26 Oct 2004 22:16:11 -0000      1.221
+++ doc/src/sgml/func.sgml      1 Nov 2004 05:19:02 -0000
@@ -6931,6 +6931,16 @@
       </tbody>
      </tgroup>
     </table>
+  <para>
+  <emphasis role="bold">NOTE:</emphasis>  Although it is not strictly a function
+    and does not appear in \df in psql, <command>ARRAY()</command>,
+    mentioned in <xref linkend="sql-syntax-array-constructors"> acts much
+    like a <literal>table function</literal> (equivalently, a
+    <literal>set-returning function</literal> or a
+    <acronym>SRF</acronym>--see <xref linkend="queries-tablefunctions">)
+    which takes <type>anyarray</type> and returns a set of
+    <type>anyelement</type>.
+  </para>
   </sect1>
  
  <sect1 id="functions-aggregate">

--5G06lTa6Jq83wMTw--