From: Bruno Wolff III <bruno@wolff.to>
To: Mike Sosteric <mikes@athabascau.ca>
Cc: pgsql-general@postgresql.org
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] arrays
Date: Mon, 30 Sep 2002 08:57:33 -0500
Message-ID: <20020930135733.GA5875@wolff.to> (raw)
In-Reply-To: <Pine.SUN.3.96.1020930063733.13580B-100000@aupair.cs.athabascau.ca>
References: <20020930122926.GA5358@wolff.to>
<Pine.SUN.3.96.1020930063733.13580B-100000@aupair.cs.athabascau.ca>
On Mon, Sep 30, 2002 at 06:38:56 -0600,
Mike Sosteric <mikes@athabascau.ca> wrote:
> On Mon, 30 Sep 2002, Bruno Wolff III wrote:
>
> The chances are very very good that in 99% of the cases we'd only ever
> have a single title. multiple titles would be rare. and, to make it worse,
> there are several instances of this where you need a table but its seems
> overkill for the odd 1% time when you actually need teh extra row.
>
> of course, the there'd be a language lookup table.
>
> what about the speed and query issue?
The book or movie or whatever table should have an index on something
(say bookid). Then make an index on the title table on bookid. This
makes getting the titles for a specific book fairly efficient.
I think using a simpler design (i.e. tables in preference to arrays)
will make doing the project easier. This may override any speed up
you get using arrays.
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: bruno@wolff.to, mikes@athabascau.ca, pgsql-general@postgresql.org
Subject: Re: [SQL] arrays
In-Reply-To: <20020930135733.GA5875@wolff.to>
* 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