Re: Proposal: stand-alone composite types - Mailing list pgsql-hackers

From Rod Taylor
Subject Re: Proposal: stand-alone composite types
Date
Msg-id 1028936788.553.3.camel@jester
Whole thread Raw
In response to Re: Proposal: stand-alone composite types  (Joe Conway <mail@joeconway.com>)
List pgsql-hackers
> > 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 :)




pgsql-hackers by date:

Previous
From: Gavin Sherry
Date:
Subject: Re: [PATCHES] CREATE TEMP TABLE .... ON COMMIT
Next
From: Yuva Chandolu
Date:
Subject: Re: Problem with lower() function