From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Darren Duncan <darren(at)darrenduncan(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: returning multiple result sets from a stored procedure |
Date: | 2010-09-09 21:47:28 |
Message-ID: | AANLkTik1nXrx0=b9Z+RoUHdbdfvv6hwi--Jz1Nn_Kw0s@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2010/9/9 Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>:
> Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>> I'm with Robert: this would be a huge extra complication for a
>> remarkably small amount of benefit.
>
> This is probably heresy, but unless it's required by the standard or
> drop-dead simple to allow, I'd be fine with *not* supporting
> overloading of stored procedure names based on argument types at
> all. I can see the need for to support it for functions; I can't
> think where it would be all that useful for stored procedures. If
> unique stored procedure names were required, it seems we might be
> able to allow assignment casts on parameters, which might be more
> useful.
>
> I'm probably missing some good use case....
for example - value transformation from / to bytea
CREATE FUNCTION send(int);
CREATE FUNCTION send(text);
CREATE FUNCTION recv(int);
CREATE FUNCTION recv(text)
then you can write
BEGIN
send('ahoj');
send(10);
recv(textvar);
recv(numvar);
Regards
Pavel Stehule
>
> -Kevin
>
From | Date | Subject | |
---|---|---|---|
Next Message | Darren Duncan | 2010-09-09 21:51:57 | Re: returning multiple result sets from a stored procedure |
Previous Message | Pavel Stehule | 2010-09-09 21:40:40 | Re: returning multiple result sets from a stored procedure |