From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Dave Page <dpage(at)postgresql(dot)org> |
Cc: | pgsql-general(at)postgresql(dot)org, Walter Vaughan <wvaughan(at)steelerubber(dot)com> |
Subject: | Re: Stored Procedure examples |
Date: | 2007-02-15 11:33:13 |
Message-ID: | 200702151233.13802.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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/
From | Date | Subject | |
---|---|---|---|
Next Message | tonylaq | 2007-02-15 11:48:55 | Re: User privilege information. |
Previous Message | Alexi Gen | 2007-02-15 11:32:44 | User privilege information. |