Jagged Rows (was Re: Proposal: real procedures again (8.4)) - Mailing list pgsql-hackers

From David Fetter
Subject Jagged Rows (was Re: Proposal: real procedures again (8.4))
Date
Msg-id 20071030151100.GW14638@fetter.org
Whole thread Raw
In response to Re: Proposal: real procedures again (8.4)  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
List pgsql-hackers
On Tue, Oct 30, 2007 at 03:24:20PM +0100, Zeugswetter Andreas ADI SD wrote:
> > > 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
> 
> The background for Quel was, that when selecting all fields from an
> inheritance hierarchy you got the additional fields of each child.
> 
> Thus the field count and types could vary within one cursor.
> Like if you would allow the following:
> select a, b::int from foo 
> union all
> select a, c::varchar, d, e from bar

This is called jagged rows, which were in Illustra, Informix, and
possibly some others.  It would be nice to have protocol-level support
for them, but it's a pretty large feature because the current Postgres
code starts off with the assumption that you know at run time the
shape of all the rows and that that shape is uniform.

Cheers,
David.
-- 
David Fetter <david@fetter.org> http://fetter.org/
Phone: +1 415 235 3778  AIM: dfetter666  Yahoo!: dfetter
Skype: davidfetter      XMPP: david.fetter@gmail.com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Per-statement Triggers (was Re: Proposal: real procedures again (8.4))
Next
From: "Filip Rembiałkowski"
Date:
Subject: Re: URGENT HELP about 'duration' stats