X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 6D7079DC82A for ; Tue, 21 Mar 2006 13:54:57 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 26804-01 for ; Tue, 21 Mar 2006 13:54:56 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from nelson.osl.com (216-21-133-120.ip.van.radiant.net [216.21.133.120]) by postgresql.org (Postfix) with ESMTP id 932A89DCC5F for ; Tue, 21 Mar 2006 13:54:52 -0400 (AST) Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: Re: plpqsql and RETURN NEXT requires a LOOP? Date: Tue, 21 Mar 2006 09:54:48 -0800 Message-ID: <144D12D7DD4EC04F99241498BB4EEDCC25E7EA@nelson.osl.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: plpqsql and RETURN NEXT requires a LOOP? Thread-Index: AcZNEAk8z3jbqGyFSzC6/5cOmlP7QQAADFqw From: "Owen Jacobson" To: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.128 required=5 tests=[AWL=0.128, UPPERCASE_25_50=0] X-Spam-Score: 0.128 X-Spam-Level: X-Archive-Number: 200603/335 X-Sequence-Number: 24681 In general, to do anything useful with RETURN NEXT you need a loop. = However, it doesn't need to be a loop over another resultset: you can do = a computation in a loop, returning values as you go. Excuse the outlook-ism. -Owen -----Original Message----- From: pgsql-sql-owner@postgresql.org = [mailto:pgsql-sql-owner@postgresql.org]On Behalf Of Davidson, Robert Sent: Tuesday, March 21, 2006 9:51 AM To: pgsql-sql@postgresql.org Subject: [SQL] plpqsql and RETURN NEXT requires a LOOP?