On Sun, Oct 31, 2004 at 10:40:47PM -0500, Tom Lane wrote:
> David Fetter <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] http://fetter.org/
phone: +1 510 893 6100   mobile: +1 415 235 3778

Remember to vote!
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">
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
      joining column's datatypes do not match

Reply via email to