From: | Andy Lewis <alewis(at)roundnoon(dot)com> |
---|---|
To: | Rich Shepard <rshepard(at)appl-ecosys(dot)com> |
Cc: | pgsql-sql(at)postgreSQL(dot)org |
Subject: | Re: [SQL] Design Question |
Date: | 1999-11-27 18:49:10 |
Message-ID: | Pine.LNX.4.05.9911271249020.8318-100000@rns.roundnoon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
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(at)appl-ecosys(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Cadiou | 1999-11-27 22:50:33 | Re: [SQL] Design Question |
Previous Message | Rich Shepard | 1999-11-27 18:41:42 | Re: [SQL] Design Question |