| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Cc: | Dave Page <dpage(at)postgresql(dot)org>, Walter Vaughan <wvaughan(at)steelerubber(dot)com> |
| Subject: | Re: Stored Procedure examples |
| Date: | 2007-02-15 09:20:42 |
| Message-ID: | 200702151020.43578.peter_e@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dave Page wrote:
> pgAdmin defines a stored procedure as:
>
> - A function on EnterpriseDB 8.0 or above, written in edbspl.
Why does EnterpriseDB determine what is a stored procedure in
PostgreSQL? Shouldn't that be limited to their own version of pgAdmin?
> - A function written in EnterpriseDB or PostgreSQL 8.1 or above with
> OUT or INOUT arguments.
What sense does that make?
> The separation (in pgAdmin) is historic, and comes from EnterpriseDB
> which treats the two object types more distinctly for Oracle
> compatibility (and had SPs before PostgreSQL).
The SQL standard does define procedures distinct from functions, and we
might want to add that someday, so that system isn't going to make
sense anymore.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashish Karalkar | 2007-02-15 09:52:19 | user input during runtime |
| Previous Message | Magnus Hagander | 2007-02-15 09:15:56 | Re: PGSQL 8.2.3 Installation problem |