From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Vladimir Dzhuvinov" <vd(at)valan(dot)net> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)? |
Date: | 2008-10-13 11:04:40 |
Message-ID: | 162867790810130404u10498c40sdf1f6554d2c2a49a@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2008/10/13 Vladimir Dzhuvinov <vd(at)valan(dot)net>:
>
>>> So, is it true that as of Postgresql 8.3 there is no way to have a
>>> pgpqsql function return multiple SELECTs?
>
>> it's true.
>
> Thank you for the definite answer, Pavel :)
>
> I came across a blog post of yours (
> http://okbob.blogspot.com/2007/11/stacked-recordset-multirecordset.html
> ) as well as several list posts indicating that multiple result sets
> might be in the working. Should I check the situation again when 8.4 is
> released?
>
I have only very raw prototype, so I am sure, so this feature will not
be in 8.4, and I am not sure about 8.5. It's nice feature, but I am
not force to complete and clean code, and I am not able create patch.
If you would do it, I am, with pleasure, send you source code, that
allows multirecord sets.
>
>> You can use setof cursors instead.
>
> Cursors, unfortunately, look cumbersome in this situation and will break
> the existing API (all transactions encapsulated within SPs, clients
> allowed to do CALL only). Anyway, thanks everyone for the cursors tip :)
>
>
> Vladimir
>
> --
> Vladimir Dzhuvinov * www.valan.net * PGP key ID AC9A5C6C
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | arnuld uttre | 2008-10-13 11:12:04 | what are those 3 passwords for ? |
Previous Message | Greg Smith | 2008-10-13 10:49:12 | Re: Improve dump and restore time |