From: Neil Conway <[EMAIL PROTECTED]>
To: Pavel Stehule <[EMAIL PROTECTED]>
CC: pgsql-patches@postgresql.org
Subject: Re: [PATCHES] return can contains any row or record functions
Date: Mon, 07 Nov 2005 18:10:13 -0500
I'm confused by this part of the patch, circa line 1835 of pl_exec.c:
/* c
I'm confused by this part of the patch, circa line 1835 of pl_exec.c:
/* coerce type if needed */
if (estate->rsi && IsA(estate->rsi, ReturnSetInfo) &&
estate->rsi->expectedDesc != NULL &&
!compatible_tupdesc(estate->rsi->expectedDesc, in_tupdesc))
{
estate->retval = (Datum) make_tuple
Neil Conway <[EMAIL PROTECTED]> writes:
> On Mon, 2005-07-11 at 14:58 +0100, Pavel Stehule wrote:
>> this patch allow using any row or record expression in return, return next
>> statement in row, record functions
> I'll review and apply this in the next day or two.
Seems like it's past time to
On Mon, 2005-07-11 at 14:58 +0100, Pavel Stehule wrote:
> this patch allow using any row or record expression in return, return next
> statement in row, record functions
I'll review and apply this in the next day or two.
-Neil
---(end of broadcast)-
Hello
this patch allow using any row or record expression in return, return next
statement in row, record functions - per request John Berkus
http://archives.postgresql.org/pgsql-hackers/2005-10/msg01350.php
regards
Pavel Stehule
___
