Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f7F2t1P20483 for ; Tue, 14 Aug 2001 22:55:01 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 102420; Tue, 14 Aug 2001 19:54:56 -0700 From: "Josh Berkus" Subject: Re: result sets from functions... To: "Robert J. Sanford, Jr." , X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Tue, 14 Aug 2001 19:54:56 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200108/200 X-Sequence-Number: 4432 Robert, > i'm reading the postgres documentation and i'm specifically > interested in creating stored procedures so that i can keep > as much of the business logic in the database as possible. > while reading 13.1.3 (SQL Functions on Composite Types) in > the Programmer's Guide i come across the phrase... > "When calling a function that returns a row, we cannot > retrieve the entire row. We must either project an > attribute out of the row or pass the entire row into > another function. > SELECT name(new_emp()) AS nobody;" Unfortunately, PostgreSQL functions do not yet return result sets. This is on the "todo" list but unfortunately requires an overhaul of how postgresql functions work. -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco