| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Rod Taylor <rbt(at)zort(dot)ca> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: stand-alone composite types |
| Date: | 2002-08-09 23:13:30 |
| Message-ID: | 3D544C9A.5060205@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2002-08-09 23:17:36 | Re: CREATE TEMP TABLE .... ON COMMIT |
| Previous Message | Rod Taylor | 2002-08-09 23:08:11 | Re: Proposal: stand-alone composite types |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gavin Sherry | 2002-08-09 23:17:36 | Re: CREATE TEMP TABLE .... ON COMMIT |
| Previous Message | Rod Taylor | 2002-08-09 23:08:11 | Re: Proposal: stand-alone composite types |