From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Ivan Sergio Borgonovo" <mail(at)webthatworks(dot)it> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: multi recordset and data type check was: Re: PL/pgSQL stored procedure returning multiple result sets (SELECTs)? |
Date: | 2008-10-13 13:16:33 |
Message-ID: | 162867790810130616s11eb08bqb67b694af910b4df@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello
2008/10/13 Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>:
> On Mon, 13 Oct 2008 15:19:33 +0300
> Vladimir Dzhuvinov <vd(at)valan(dot)net> wrote:
>
>> Well, (in MySQL at least) in that case you're still going to get a
>> result set, it's just going to be an empty one (result with no
>> rows).
>
>> So, no matter how many rows the SELECT statements resolve to,
>> you're always going to get two result sets :)
>
> It seems anyway that the usefulness of this feature largely depends
> on the language library.
> eg. I can't see a way to support it with php right now but it is
> supported by python.
> Am I missing something?
>
> Out of curiosity, what language are you using?
I know so multirecordsets are well supported for php and MySQL, and in
all Microsoft environments - Microsoft SQL Server use it very hard.
These functionality has lot of advantage, mainly in stateless
environment like plpgsql.
regards
Pavel Stehule
>
> --
> Ivan Sergio Borgonovo
> http://www.webthatworks.it
>
>
> --
> Sent via pgsql-general mailing list (pgsql-general(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
>
From | Date | Subject | |
---|---|---|---|
Next Message | justin | 2008-10-13 13:34:45 | Re: Chart of Accounts |
Previous Message | ries van Twisk | 2008-10-13 13:02:15 | Re: Drupal and PostgreSQL - performance issues? |