Skip site navigation (1) Skip section navigation (2)

Re: Proposal: real procedures again (8.4)

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: 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-29 22:32:11
Message-ID: 20071029223211.GB19726@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-hackers
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;

in a plpgsql function, and getting two result sets (I'm fuzzy about the
exact syntax but you get the idea).  Can this be done at all?  

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.

In response to

Responses

pgsql-hackers by date

Next:From: James MansionDate: 2007-10-29 22:32:44
Subject: Re: Proposal: real procedures again (8.4)
Previous:From: Gregory StarkDate: 2007-10-29 22:18:17
Subject: Re: Proposal: real procedures again (8.4)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group