| From: | Rod Taylor <rbt(at)zort(dot)ca> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| 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:46:28 |
| Message-ID: | 1028936788.553.3.camel@jester |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> > 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 :)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yuva Chandolu | 2002-08-09 23:49:50 | Re: Problem with lower() function |
| Previous Message | Dann Corbit | 2002-08-09 23:18:14 | Re: Proposal: stand-alone composite types |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2002-08-10 00:26:30 | Re: Proposal: stand-alone composite types |
| Previous Message | Gavin Sherry | 2002-08-09 23:17:36 | Re: CREATE TEMP TABLE .... ON COMMIT |