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

From Joe Conway
Subject Re: Proposal: stand-alone composite types
Date
Msg-id 3D544C9A.5060205@joeconway.com
Whole thread Raw
In response to Re: Proposal: stand-alone composite types  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: Proposal: stand-alone composite types  (Rod Taylor <rbt@zort.ca>)
List pgsql-hackers
Rod Taylor wrote:
> I think it buys the same as SERIAL does for sequences.

That's a great analogy.

> 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.

Joe



pgsql-hackers by date:

Previous
From: Rod Taylor
Date:
Subject: Re: Proposal: stand-alone composite types
Next
From: "Dann Corbit"
Date:
Subject: Re: Proposal: stand-alone composite types