From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Josh Berkus <josh(at)agliodbs(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jan Wieck <JanWieck(at)yahoo(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, "David E(dot) Wheeler" <david(at)justatheory(dot)com>, pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PL/pgSQL PERFORM with CTE |
Date: | 2013-08-23 20:51:35 |
Message-ID: | CAFj8pRAMdoJEKeTm4Ncpn1+ikEbsKd0HSFseJ+mDS+8Ud1fyCQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/8/23 Josh Berkus <josh(at)agliodbs(dot)com>
> On 08/23/2013 11:30 AM, Pavel Stehule wrote:
> > 2013/8/23 Josh Berkus <josh(at)agliodbs(dot)com>
> >
> >> Pavel,
> >>
> >>> But it can have a different reason. In T-SQL (Microsoft or Sybase) or
> >> MySQL
> >>> a unbound query is used to direct transfer data to client side.
> >>
> >> Are you planning to implement that in PL/pgSQL?
> >>
> >>
> > yes. I would to see a stored procedures with this functionality in pg
>
> Is there some reason we wouldn't use RETURN QUERY in that case, instead
> of SELECT? As I said above, it would be more consistent with existing
> PL/pgSQL.
>
for example - multirecordset support. can be reason why distinguish between
these syntax and these functionality.
Regards
Pavel
>
> --
> Josh Berkus
> PostgreSQL Experts Inc.
> http://pgexperts.com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2013-08-23 21:08:30 | Re: Redesigning checkpoint_segments |
Previous Message | Josh Berkus | 2013-08-23 20:08:33 | Re: PL/pgSQL PERFORM with CTE |