Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f3I4OJu18741 for ; Wed, 18 Apr 2001 00:24:19 -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 41031; Tue, 17 Apr 2001 21:24:18 -0700 From: "Josh Berkus" Subject: Re: Re: Same question about PostgreSql To: Nils Zonneveld , pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Tue, 17 Apr 2001 21:24:18 -0700 Message-ID: In-Reply-To: <3ADCC2D0.5BAB0A25@mbit.nl> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200104/296 X-Sequence-Number: 2652 Nils, > I always thought that Pl/PgSQL functions where 'stored procedures'. > Probably I'm wrong, but whats the difference between a Pl/PgSQL > function > and a stored procedure? (just curious). Postgres functions have really expanded the concept of function, to the point of *almost* being stored procedures. However, there are still a few things missing: 1. Stored procedures must be able to return a rowset, possibly mutiple rowsets. 2. Stored procedures usually accept an indefinite number of parameters. 3. Stored procedures should be capable of logging their activites. 4. Stored procedures should have access to the full range of DB control language, includign cursors, transactions, and error handling. Of the 4. I'm only certain that 1. is part of the SQL92 spec. Any more authoritative opinions? -Josh ______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