pg.ddx.io pgsql-sql@postgresql.org mailing list archive
help / color / mirror / Atom feedDesign Question
6+ messages / 4 participants
[nested] [flat]
* Design Question
@ 1999-11-27 18:25 Andy Lewis <alewis@roundnoon.com>
0 siblings, 2 replies; 6+ messages in thread
From: Andy Lewis @ 1999-11-27 18:25 UTC (permalink / raw)
To: pgsql-sql
Hello All!
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?
Thanks!
Andy
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [SQL] Design Question
@ 1999-11-27 18:41 Rich Shepard <rshepard@appl-ecosys.com>
parent: Andy Lewis <alewis@roundnoon.com>
1 sibling, 2 replies; 6+ messages in thread
From: Rich Shepard @ 1999-11-27 18:41 UTC (permalink / raw)
To: Andy Lewis <alewis@roundnoon.com>; +Cc: pgsql-sql
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [SQL] Design Question
@ 1999-11-27 18:49 Andy Lewis <alewis@roundnoon.com>
parent: Rich Shepard <rshepard@appl-ecosys.com>
1 sibling, 0 replies; 6+ messages in thread
From: Andy Lewis @ 1999-11-27 18:49 UTC (permalink / raw)
To: Rich Shepard <rshepard@appl-ecosys.com>; +Cc: 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@appl-ecosys.com
>
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [SQL] Design Question
@ 1999-11-27 22:50 Julien Cadiou <julienc@vicnet.net.au>
parent: Andy Lewis <alewis@roundnoon.com>
1 sibling, 0 replies; 6+ messages in thread
From: Julien Cadiou @ 1999-11-27 22:50 UTC (permalink / raw)
To: Andy Lewis <alewis@roundnoon.com>; +Cc: pgsql-sql
Hi Andy,
actually, the postgres site has pretty much what you're after I think.
If you go under documentation, and going through the "tutorial", the example they use is quite similar (if I remember correctly) to what you're after ...
Cheers,
At 12:25 27/11/1999 -0600, you wrote:
>Hello All!
>
>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?
>
>Thanks!
>
>Andy
>
>
>************
>
>
>
<bold>Julien CADIOU
</bold>Database Administrator
<bold>VICNET</bold> - Victoria's network
Phone: (03) 9669 9710
Fax: (03) 9669 9805
Web: http://www.vicnet.net.au/
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [SQL] Design Question
@ 1999-11-28 19:23 De Moudt Walter <wdemoudt@planetinternet.be>
parent: Rich Shepard <rshepard@appl-ecosys.com>
1 sibling, 1 reply; 6+ messages in thread
From: De Moudt Walter @ 1999-11-28 19:23 UTC (permalink / raw)
To: Rich Shepard <rshepard@appl-ecosys.com>; +Cc: Andy Lewis <alewis@roundnoon.com>; pgsql-sql
Hi Rich,
I think that if you :
- create one table "brokers" with the broker's name (let's call that
broker_name) and a unique id (just in case two show up with the same
name, there are many Smiths, isn't it ?). The ID could be an integer
up-counting number (1 for the first, 2 for the second, ...), let's call
that field broker_id.
-create a second table "locations" which contains all nessecary fields
for a certain location of a certain broker (street, mailbox, city,
state, ..) AND a field broker_id, which should have the same integer as
the broker_id of the broker's table.
Now the name of the broker only appears once in the brokers table. So
even if the broker's company should be called "John Smiths Absolutely
Marvellous and undoubtedly honest stock trade company", and have 50
houses all over the states, this name only takes disk space once. And
that's one of the objectives of relational databases : limit the
occurance of extensive and repeating data by writing it once, and then
pointing to it, instead of writing it again and again.
You should take care, however, that the datatype for broker_id is the
same in both tables ! So, if you use an integer for it in the brokers
table, then use an integer type in the locations table as well !
Hope this explains something :-) It's only the tip of the veil, of
course. If this interrests you, you should really buy a book on
relational databases.
Toi,
Walter De Moudt
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
>
> ************
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: [SQL] Design Question
@ 1999-11-28 20:56 Andy Lewis <alewis@roundnoon.com>
parent: De Moudt Walter <wdemoudt@planetinternet.be>
0 siblings, 0 replies; 6+ messages in thread
From: Andy Lewis @ 1999-11-28 20:56 UTC (permalink / raw)
To: De Moudt Walter <wdemoudt@planetinternet.be>; +Cc: Rich Shepard <rshepard@appl-ecosys.com>; pgsql-sql
Yes, thanks!
Andy
On Sun, 28 Nov 1999, De Moudt Walter wrote:
> Hi Rich,
>
> I think that if you :
> - create one table "brokers" with the broker's name (let's call that
> broker_name) and a unique id (just in case two show up with the same
> name, there are many Smiths, isn't it ?). The ID could be an integer
> up-counting number (1 for the first, 2 for the second, ...), let's call
> that field broker_id.
>
> -create a second table "locations" which contains all nessecary fields
> for a certain location of a certain broker (street, mailbox, city,
> state, ..) AND a field broker_id, which should have the same integer as
> the broker_id of the broker's table.
>
> Now the name of the broker only appears once in the brokers table. So
> even if the broker's company should be called "John Smiths Absolutely
> Marvellous and undoubtedly honest stock trade company", and have 50
> houses all over the states, this name only takes disk space once. And
> that's one of the objectives of relational databases : limit the
> occurance of extensive and repeating data by writing it once, and then
> pointing to it, instead of writing it again and again.
>
> You should take care, however, that the datatype for broker_id is the
> same in both tables ! So, if you use an integer for it in the brokers
> table, then use an integer type in the locations table as well !
>
> Hope this explains something :-) It's only the tip of the veil, of
> course. If this interrests you, you should really buy a book on
> relational databases.
>
> Toi,
> Walter De Moudt
> 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
> >
> > ************
>
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~1999-11-28 20:56 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-11-27 18:25 Design Question Andy Lewis <alewis@roundnoon.com>
1999-11-27 18:41 ` Rich Shepard <rshepard@appl-ecosys.com>
1999-11-27 18:49 ` Andy Lewis <alewis@roundnoon.com>
1999-11-28 19:23 ` De Moudt Walter <wdemoudt@planetinternet.be>
1999-11-28 20:56 ` Andy Lewis <alewis@roundnoon.com>
1999-11-27 22:50 ` Julien Cadiou <julienc@vicnet.net.au>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox