Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 88D88475C85 for ; Mon, 30 Sep 2002 09:49:11 -0400 (EDT) Received: from wolff.to (wolff.to [66.93.197.35]) by postgresql.org (Postfix) with SMTP id B092D475C60 for ; Mon, 30 Sep 2002 09:49:10 -0400 (EDT) Received: (qmail 6083 invoked by uid 500); 30 Sep 2002 13:57:33 -0000 Date: Mon, 30 Sep 2002 08:57:33 -0500 From: Bruno Wolff III To: Mike Sosteric Cc: pgsql-general@postgresql.org, pgsql-sql@postgresql.org Subject: Re: [SQL] arrays Message-ID: <20020930135733.GA5875@wolff.to> Mail-Followup-To: Mike Sosteric , pgsql-general@postgresql.org, pgsql-sql@postgresql.org References: <20020930122926.GA5358@wolff.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.25i X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/1373 X-Sequence-Number: 30954 On Mon, Sep 30, 2002 at 06:38:56 -0600, Mike Sosteric 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.