| From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca>, Aaron Bono <postgresql(at)aranya(dot)com> |
| Cc: | phillips(at)weatherbeeta(dot)com(dot)au, pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: COPY to table with array columns (Longish) |
| Date: | 2006-06-13 03:51:20 |
| Message-ID: | 20060613035120.15910.qmail@web31804.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
> On Mon, 2006-06-12 at 21:58 -0500, Aaron Bono wrote:
> > I agree with Tom. Personally I cannot think of a time I would use an
> > array column over a child table. Maybe someone can enlighten me on
> > when an array column would be a good choice.
>
> Arrays are a good choice when the data comes naturally segmented.
>
Also, for a case and point, some of the postgresql system tables use arrays. I suppose that these
would be examples were the core develops felt arrays were a good fit.
Regards,
Richard Broersma Jr.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aaron Bono | 2006-06-13 04:11:43 | Re: COPY to table with array columns (Longish) |
| Previous Message | Rod Taylor | 2006-06-13 03:18:51 | Re: COPY to table with array columns (Longish) |