Re: Stored Procedure examples - Mailing list pgsql-general

From Peter Eisentraut
Subject Re: Stored Procedure examples
Date
Msg-id 200702151233.13802.peter_e@gmx.net
Whole thread Raw
In response to Re: Stored Procedure examples  (Dave Page <dpage@postgresql.org>)
Responses Re: Stored Procedure examples  (Dave Page <dpage@postgresql.org>)
List pgsql-general
Dave Page wrote:
> Because PostgreSQL allows return values and IN/OUT/INOUT parameters
> on the same routine, we use the first part of the definition only
> when making our distinction.
>
> Source: section 4.27, SQL-invoked Routines in
> SWD-02-Foundation-2003-09

That same clause also contains various arguments against pgAdmin's
definition.  For example, all procedures must be invoked using the CALL
statement, which PostgreSQL doesn't have.  But that is not the point.
If you were writing sqlAdmin, then I'd say you are right.  But in
PostgreSQL we have made conscious efforts to present all programming
interfaces under a uniform "function" label, so I think it does users a
disservice if the GUI handles it differently.

For that matter, what is supposed to be the practical benefit of this
distinction?

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: missing FROM-clause
Next
From: "Alexi Gen"
Date:
Subject: User privilege information.