Re: proposal: table functions and plpgsql

From: Hannu Krosing <hannu(at)krosing(dot)net>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: table functions and plpgsql
Date: 2008-05-22 13:01:55
Message-ID: 1211461315.7816.1.camel@huvostro
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, 2008-05-21 at 23:06 +0200, Pavel Stehule wrote:
> 2008/5/21 Hannu Krosing <hannu(at)krosing(dot)net>:
> > On Wed, 2008-05-21 at 13:31 -0400, Merlin Moncure wrote:
> >> On Wed, May 21, 2008 at 1:28 PM, Hannu Krosing <hannu(at)krosing(dot)net> wrote:
> >> >> In my proposal I don't create any default variables. Result type is
> >> >> only virtual - I don't need write it to system directory. I thing it's
> >> >> better than using some specific predeclared type as RESULTTYPE OR
> >> >> RESULTSET.
> >> >
> >> > How is this different from using OUT params and RETURNS SETOF RECORD ?
> >>
> >> *) you reference output variables via rowtype (r.var vs. var)
> >
> > As I'm currently working on updating another pl (pl/python), I'd like to
> > know how will this affect get_call_result_type() defined in funcapi.h.
> > will there be an extra parameter for record name there ?
>
> no

why not ?

do you think that other pl languages won't need it ?

---------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-05-22 13:31:42 Re: idea: storing view source in system catalogs
Previous Message Pierre-Yves Strub 2008-05-22 11:31:55 Re: Fragments in tsearch2 headline