Received: from rns.roundnoon.com (alewis@[204.0.130.147]) by hub.org (8.9.3/8.9.3) with ESMTP id NAA32551 for ; Sat, 27 Nov 1999 13:50:32 -0500 (EST) (envelope-from alewis@roundnoon.com) Received: from localhost (alewis@localhost) by rns.roundnoon.com (8.9.1/8.9.3) with ESMTP id MAA08320; Sat, 27 Nov 1999 12:49:10 -0600 Date: Sat, 27 Nov 1999 12:49:10 -0600 (CST) From: Andy Lewis To: Rich Shepard cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Design Question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Thanks, will do.... On Sat, 27 Nov 1999, Rich Shepard wrote: > On Sat, 27 Nov 1999, Andy Lewis wrote: > > > Lets say that I have a DB that I am using to save address info on > > different brokers. Broker name, address, city, state, zip > > > > Some brokers have representation in different states. > > > > How would I be able to save that info so that it can be later selected by > > users looking for a broker in a certain state(s)? > > > > What type of field/table/DB could I save that in for easy reference? > > Andy, > > I suggest that you buy (or borrow from a library) a book on relational > data base design. To give you the simple answer to your question: have one > table for the broker's name and identification and a separate table for > their addresses. It's called a many-to-one structure and is created by > normalizing the data. > > Rich > > Dr. Richard B. Shepard, President > > Applied Ecosystem Services, Inc. (TM) > Making environmentally-responsible mining happen. (SM) > -------------------------------- > 2404 SW 22nd Street | Troutdale, OR 97060-1247 | U.S.A. > + 1 503-667-4517 (voice) | + 1 503-667-8863 (fax) | rshepard@appl-ecosys.com >