From: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
---|---|
To: | Neil Conway <neilc(at)samurai(dot)com> |
Cc: | PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: first cut at PL/PgSQL table functions |
Date: | 2002-08-20 13:32:31 |
Message-ID: | 3D6244EF.FB8069DC@Yahoo.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Neil Conway wrote:
>
> The attached patch is my first attempt at implementing table functions
> for PL/PgSQL.
> [...]
>
> - inside PL/PgSQL, the application developer can add another
> tuple to the result set by using RETURN NEXT. PL/PgSQL takes
> care of creating a tuple store, etc etc.
If memory serves, the syntax another major database is using is
RETURN ... AND RESUME;
And you're right, the parser is a nightmare. Sorry for that.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2002-08-20 14:10:22 | Re: first cut at PL/PgSQL table functions |
Previous Message | Tom Lane | 2002-08-20 13:14:27 | Re: first cut at PL/PgSQL table functions |