Re: [SQL] arrays

From: Bruno Wolff III <bruno(at)wolff(dot)to>
To: Mike Sosteric <mikes(at)athabascau(dot)ca>
Cc: pgsql-general(at)postgresql(dot)org, pgsql-sql(at)postgresql(dot)org
Subject: Re: [SQL] arrays
Date: 2002-09-30 13:57:33
Message-ID: 20020930135733.GA5875@wolff.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-sql

On Mon, Sep 30, 2002 at 06:38:56 -0600,
Mike Sosteric <mikes(at)athabascau(dot)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.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Johnson, Shaunn 2002-09-30 14:00:04 Errors reloading with pg_dump
Previous Message thimoty@thimoty.it 2002-09-30 13:43:22 stale temporary tables

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Sullivan 2002-09-30 14:31:38 Re: Cause of missing pg_clog files
Previous Message Jim Buttafuoco 2002-09-30 13:24:28 Re: How to REINDEX in high volume environments?

Browse pgsql-sql by date

  From Date Subject
Next Message Tom Lane 2002-09-30 14:42:08 Re: [SQL] arrays
Previous Message Achilleus Mantzios 2002-09-30 13:18:54 Re: [SQL] arrays