Re: anonymous composite types for Table Functions (aka

Tom Lane wrote:
> Okay. I have patches to fix the domain-type issues, and will commit
> as soon as I've finished testing 'em.

Thanks.

>
> I would suggest that either gram.y or someplace early in the analyzer
> should transpose the names from the coldeflist into the "user specified
> alias" structure. That should fix the alias naming issues. The other
> issues indicate that if a coldeflist is provided, you should check it
> against the function return type in all cases not only RECORD. In the
> non-RECORD cases it could be done in the parse analysis phase.

Actually, I was just looking at this and remembering that I wanted to
disallow a coldeflist for non-RECORD return types. Do you prefer to
allow it (but properly apply the alias and enforce the type)?

Joe