Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:

From: Joe Conway <mail(at)joeconway(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Date: 2002-12-30 00:58:00
Message-ID: 3E0F9A18.8030005@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>>The problem with the Berkley approach is what to do if there are two SRFs in
>>the target list.
>
> Agreed. The Berkeley code (or more accurately, the descendant code
> that's in our source tree) generates the cross product of the rows
> output by the SRFs, but I've never understood why that should be a good
> approach to take. I could live with just rejecting multiple SRFs in the
> same targetlist --- at least till someone comes up with a convincing
> semantics for such a thing.
>

I would like to start spending some time digging in to this. Any pointers or
thoughts on the best way to implement it? A little direction might save me
days of wheel spinning :-).

Thanks,

Joe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-12-30 01:05:37 Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Previous Message Kevin Brown 2002-12-30 00:39:37 Re: MOVE strangeness

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2002-12-30 01:05:37 Re: [Fwd: SETOF input parameters (was Re: [HACKERS] proposal:
Previous Message Kevin Brown 2002-12-30 00:39:37 Re: MOVE strangeness