Maybe change in backend to treat complex types marked in relation as
COMPLEX in same way as scalar values is solution, actually I don't know.
This can be determined by GUC variable so every one can be happy :)
On Thu, 17 Feb 2011 23:08:13 +1300, Oliver Jowett wrote:
> Lukas Eder wrote:
>
>> The result set meta data correctly state that there are 6 OUT
>> columns. But only the first 2 are actually fetched (because of a
>> nested UDT)...
>
> The data mangling was just a plpgsql syntactic issue, wasn't it?
>
> Oliver
