Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E10712E168C for ; Wed, 28 Nov 2007 05:48:28 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 15312-02-3 for ; Wed, 28 Nov 2007 05:48:24 -0400 (AST) Received: from sd-2317.dedibox.fr (sd-2317.dedibox.fr [88.191.17.192]) by postgresql.org (Postfix) with ESMTP id 610FD2E01AC for ; Wed, 28 Nov 2007 05:48:21 -0400 (AST) Received: from sd-2317.dedibox.fr (localhost.localdomain [127.0.0.1]) by sd-2317.dedibox.fr (Postfix) with ESMTP id 76AB3F27B; Wed, 28 Nov 2007 10:48:19 +0100 (CET) Received: from [192.168.10.1] (ASte-Genev-Bois-153-1-31-100.w83-112.abo.wanadoo.fr [83.112.77.100]) by sd-2317.dedibox.fr (Postfix) with ESMTP id 47C701D7F; Wed, 28 Nov 2007 10:48:19 +0100 (CET) Message-ID: <474D3962.2070709@lelarge.info> Date: Wed, 28 Nov 2007 10:48:18 +0100 From: Guillaume Lelarge User-Agent: Thunderbird 2.0.0.6 (X11/20071022) MIME-Version: 1.0 To: Neil Conway CC: pgsql-docs@postgresql.org Subject: Re: Two fixes for plpgsql.sgml References: <474D160D.5090908@lelarge.info> <1196242488.10373.13.camel@goldbach> In-Reply-To: <1196242488.10373.13.camel@goldbach> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV using ClamSMTP X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200711/95 X-Sequence-Number: 4628 Neil Conway a écrit : > On Wed, 2007-11-28 at 08:17 +0100, Guillaume Lelarge wrote: >> This patch fixes two issues on plpgsql.sgml. > > The first hunk seems like a regression to me: AFAICS the current > phrasing is what is intended. > > *** 133,139 **** > > > PL/pgSQL functions can also be declared to return > ! a set, or table, of any data type they can return a > single > instance of. Such a function generates its output by executing > RETURN NEXT for each desired element of the result > set, or by using RETURN QUERY to output the result of > --- 133,139 ---- > > > PL/pgSQL functions can also be declared to return > ! a set, or table, or any data type they can return a > single > instance of. Such a function generates its output by executing > RETURN NEXT for each desired element of the result > set, or by using RETURN QUERY to output the result of > That's why I said that it needs to be reviewed carefully :) It just means I didn't understand the sentence. Can you explain why the last part is needed ? (the part that starts with "of any data type...") Thanks. -- Guillaume. http://www.postgresqlfr.org http://dalibo.com