Hannu Krosing wrote:
On Sun, 2002-05-26 at 21:55, Joe Conway wrote:
Tom Lane wrote:
3. PL/pgSQL support for returning sets -- this seems to me like an
important item if SRFs are to be useful to the masses. Any pointers on
how to approach this would be appreciated.
Does Oracle's pl/sql
Tom Lane wrote:
3. PL/pgSQL support for returning sets -- this seems to me like an
important item if SRFs are to be useful to the masses. Any pointers on
how to approach this would be appreciated.
Does Oracle's pl/sql support this? If so what does it look like?
Oracle supports pipelined
FOR row IN select_query LOOP
statements
RETURN NEXT row;
END LOOP;
Informix has
RETURN x1, x2, x3 WITH RESUME;
This seems reasonable to me. PostgreSQL could also allow
return x with resume, where x is already a composite type.
Andreas
---(end of
Tom Lane wrote:
3. PL/pgSQL support for returning sets -- this seems to me like an
important item if SRFs are to be useful to the masses. Any pointers on
how to approach this would be appreciated.
Does Oracle's pl/sql support this? If so what does it look like?
I *think* Oracle pl/sql can
Joe Conway [EMAIL PROTECTED] writes:
I'm thinking about next steps for SRFs and looking for input. ... At
this point I know of several things which need to be done (or at least I
think they are desirable):
1. Documentation -- it wasn't clear if Joel Burton was going to have
time to
Joe Conway wrote:
Tom Lane wrote:
Now that I think about it, it's possible that ExecFunctionReScan is
correct now, at least given the simplistic always-materialize policy
that we've implemented so far. But it hasn't gotten much testing.
OK -- the attached (stand alone) test script
was Re: [PATCHES] SRF patch (was Re: [HACKERS] troubleshooting pointers)
Tom Lane wrote:
Now that I think about it, it's possible that ExecFunctionReScan is
correct now, at least given the simplistic always-materialize policy
that we've implemented so far. But it hasn't gotten much
