Re: Function returns composite type

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Teodor Sigaev <teodor(at)sigaev(dot)ru>
Cc: Joe Conway <mail(at)joeconway(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Function returns composite type
Date: 2003-06-11 16:37:46
Message-ID: 19785.1055349466@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Forest Wilkinson 2003-06-11 16:52:48 Re: How to enumerate foreign key constraints after migrating from 7.1.3?
Previous Message Teodor Sigaev 2003-06-11 16:26:01 Re: Function returns composite type