Re: Proposal: real procedures again (8.4)

From: "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>
To: "Gregory Stark" <stark(at)enterprisedb(dot)com>, "Hannu Krosing" <hannu(at)skype(dot)net>, "David Fetter" <david(at)fetter(dot)org>, "Josh Berkus" <Josh(dot)Berkus(at)sun(dot)com>, "Merlin Moncure" <mmoncure(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal: real procedures again (8.4)
Date: 2007-10-30 08:40:56
Message-ID: 162867790710300140n4be87a4oe8ef8c55882893ac@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

2007/10/29, Alvaro Herrera <alvherre(at)commandprompt(dot)com>:
> Gregory Stark wrote:
> > "Hannu Krosing" <hannu(at)skype(dot)net> writes:
> >
> > > What I was referring to, was a "code cleanup" of libpq several years
> > > ago, when someone (maybe Bruce IIRC) removed ability to accept multiple
> > > recordsets from backend altogether, on the basis that it is not used
> > > anyway.
> >
> > You can still receive multiple record sets just fine using libpq. psql doesn't
> > handle them but they're there. When I was doing the concurrent psql patch I
> > also had it handling multiple record sets.
> >
> > Something else you may be thinking of, I don't think it's legal to do queries
> > like "select 1 ; select 2" in the new protocol. That was legal in the old
> > protocol.
>
> I think the cool thing that Josh Berkus wants is
>
> return query select a, b, c from foo;
> return query select d, e, f from bar;
>

maybe better

SELECT a,b FROM foo;
SELECT d, e FROM bar;

procedure doesn't need return statement usually

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2007-10-30 08:48:24 Re: Proposal: real procedures again (8.4)
Previous Message sayali k 2007-10-30 07:53:21 Multiple trees in parsetree_list