Re: Function returns composite type - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Function returns composite type
Date
Msg-id 19785.1055349466@sss.pgh.pa.us
Whole thread Raw
In response to Re: Function returns composite type  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-hackers
>> We've discussed a couple of times allowing the parser to "interrogate" 
>> the function at parse time to let it determine what the runtime tupdesc 
>> will be, but I haven't been able to come up with a good way to do that.

This seems fairly unworkable to me, as in interesting cases the parser
could not find out what parameter values to pass to the function, so the
function wouldn't have enough information to know what it will return
either.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Teodor Sigaev
Date:
Subject: Re: Function returns composite type
Next
From: Forest Wilkinson
Date:
Subject: Re: [GENERAL] How to enumerate foreign key constraints after migrating from 7.1.3?