From: Richard Broersma Jr <rabroersma@yahoo.com>
To: Rod Taylor <pg@rbt.ca>
To: Aaron Bono <postgresql@aranya.com>
Cc: phillips@weatherbeeta.com.au
Cc: pgsql-sql@postgresql.org
Subject: Re: COPY to table with array columns (Longish)
Date: Mon, 12 Jun 2006 20:51:20 -0700 (PDT)
Message-ID: <20060613035120.15910.qmail@web31804.mail.mud.yahoo.com> (raw)
In-Reply-To: <1150168731.73622.10.camel@home>
> 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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: rabroersma@yahoo.com, pg@rbt.ca, postgresql@aranya.com, phillips@weatherbeeta.com.au
Subject: Re: COPY to table with array columns (Longish)
In-Reply-To: <20060613035120.15910.qmail@web31804.mail.mud.yahoo.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox