Re: Proposal: stand-alone composite types

> > Is it likely to have more than one function using a complex type like
> > that?  If not, then allowing it's creation (not enforcing) could be
> > useful.
> 
> That's what I was thinking. In cases where you want to use the type for 
> several functions, use CREATE TYPE. If you only need the type for one 
> function, let the function creation process manage it for you.

So long as the type dissapears with the drop of the function.  But don't
make stuff you don't clean up :)