| From: | Josh Berkus <josh(at)agliodbs(dot)com> | 
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org | 
| Subject: | Re: "stored procedures" | 
| Date: | 2011-04-21 17:22:25 | 
| Message-ID: | 4DB067D1.1050002@agliodbs.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-hackers | 
Peter,
> I would like to collect some specs on this feature.  So does anyone have
> links to documentation of existing implementations, or their own spec
> writeup?  A lot of people appear to have a very clear idea of this
> concept in their own head, so let's start collecting those.
Delta between SPs and Functions for PostgreSQL:
* SPs are executed using CALL or EXECUTE, and not SELECT.
* SPs do not return a value
** optional: SPs *may* have OUT parameters.
* SPs have internal transactions including begin/commit
** optional: SPs can run non-transaction statements,
   like CREATE INDEX CONCURRENTLY and VACUUM
** corollary: SPs may not be called as part of a larger query
** question: if an SP is called by another SP, what is its
   transaction context?
* optional: SPs can return multisets (ala SQL Server).
** question: how would multisets be handled on the client end?
-- 
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2011-04-21 17:34:00 | Re: "stored procedures" | 
| Previous Message | David E. Wheeler | 2011-04-21 17:20:27 | Re: my signature |