Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id C3E2D4761D0 for ; Mon, 30 Sep 2002 12:00:36 -0400 (EDT) Received: from bast.unixathome.org (bast.unixathome.org [216.187.105.150]) by postgresql.org (Postfix) with ESMTP id BF4B347607D for ; Mon, 30 Sep 2002 12:00:35 -0400 (EDT) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 218813F4B; Mon, 30 Sep 2002 12:00:40 -0400 (EDT) From: "Dan Langille" To: "Josh Berkus" , Mike Sosteric Date: Mon, 30 Sep 2002 11:59:12 -0400 MIME-Version: 1.0 Subject: Re: [GENERAL] arrays Cc: pgsql-sql@postgresql.org Message-ID: <3D983C90.7277.7FF06CB4@localhost> In-reply-to: References: X-mailer: Pegasus Mail for Windows (v4.02) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200209/419 X-Sequence-Number: 9696 On 30 Sep 2002 at 8:54, Josh Berkus wrote: > As such, I'd reccommend one of two approaches for you: > > 1) Post some of your schema ideas here, and let us show you how they > are better done relationally. The relational data model has 30 years > of thought behind it -- it can solve a lot of problems. Mike, Just in case you or others think Josh is some crazed lunatic[1] who doesn't know what he's talking about, I support his views on this topic. Avoid arrays. Normalize your data. [1] - Actually, I don't think I know anything about Josh, except that he's right about normalizing your data. -- Dan Langille I'm looking for a computer job: http://www.freebsddiary.org/dan_langille.php