Re: Python setof patch

From: Michael Fuhr <mike(at)fuhr(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Gerrit van Dyk <gvandyk(at)agileworks(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Python setof patch
Date: 2005-07-05 17:28:09
Message-ID: 20050705172809.GA98212@winnie.fuhr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

On Tue, Jul 05, 2005 at 01:14:25PM -0400, Tom Lane wrote:
>
> Aside from minor problems like being broken and undocumented, there is a
> more serious question here: is this even the functionality we want?

I'd rather see something akin to PL/pgSQL's RETURN NEXT or PL/Perl's
return_next.

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Jim C. Nasby 2005-07-05 17:43:55 Re: [PATCHES] HEAD doesn't cope with libraries in non-default
Previous Message Tom Lane 2005-07-05 17:14:25 Re: Python setof patch