| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Asko Oja <ascoja(at)gmail(dot)com>, "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Out parameters handling |
| Date: | 2009-03-06 22:57:43 |
| Message-ID: | 20090306225743.GL3901@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kevin Grittner escribió:
> I find the PostgreSQL implementation of OUT parameters, well,
> surprising. I've used databases where stored procedures can have a
> RETURN value, OUT parameters, and result streams as three discreet
> things which can't be mistaken for one another -- which seems more
> sensible. Is this issue in PostgreSQL a spin-off of not having stored
> procedures, and trying to shoehorn SP behavior into functions?
I think the current behavior is more a result of Postgres not having
host variables.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas 'ads' Scherbaum | 2009-03-06 23:42:40 | Re: Validating problem in the isn contrib module |
| Previous Message | Kevin Grittner | 2009-03-06 22:13:43 | Re: Out parameters handling |