| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCHES] Arrays of Complex Types |
| Date: | 2007-05-06 17:47:32 |
| Message-ID: | 20070506174732.GC29535@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
On Sun, May 06, 2007 at 01:33:47PM -0400, Andrew Dunstan wrote:
> However, there are still some oddities. For example, a change to or
> removal of the base type affects the array type, but the array type
> can be directly operated on (e.g. alter type _aa set schema foo ).
> I'm inclined to say we should prevent direct operations on array
> types, and they should live or die by their parent types.
>
> Thoughts?
+1 on binding the array types tightly to the parent types.
Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
Consider donating to PostgreSQL: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-05-06 18:31:53 | Re: Integer datetimes |
| Previous Message | Andrew Dunstan | 2007-05-06 17:33:47 | Re: [PATCHES] Arrays of Complex Types |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-05-07 01:11:55 | Re: Enable integer datetimes by default |
| Previous Message | Andrew Dunstan | 2007-05-06 17:33:47 | Re: [PATCHES] Arrays of Complex Types |