> Seems reasonable to me. A SRF function really ought to explicitly set
> isDone on every call anyway.
Aye, it seems reasonable, but a bit inconsistent with the effect of
ExecMakeFunctionResult, which does the same thing but bases the continuity of
the result gathering on the isDone pointer, whic
James William Pye <[EMAIL PROTECTED]> writes:
> While I was finishing up SRF support in PL/Py, I noticed that when VPC is the
> selected mode for a table function, ExecMakeTableFunctionResult will set
> rsinfo.isDone to ExprSingleResult each time it loops to fetch another value
> (when a direct_fun
Greets,
While I was finishing up SRF support in PL/Py, I noticed that when VPC is the
selected mode for a table function, ExecMakeTableFunctionResult will set
rsinfo.isDone to ExprSingleResult each time it loops to fetch another value
(when a direct_function_call). This makes the VPC-SRF author se
